Triple
T38309862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-in-Wonder |
E1033653
|
entity |
| Predicate | featureCombination |
P40827
|
FINISHED |
| Object | 3D acceleration and TV tuner |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 3D acceleration and TV tuner | Statement: [All-in-Wonder, featureCombination, 3D acceleration and TV tuner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureCombination Context triple: [All-in-Wonder, featureCombination, 3D acceleration and TV tuner]
-
A.
combinesFeaturesOf
Indicates that one entity integrates or merges characteristics, attributes, or functionalities originating from multiple other entities.
-
B.
combinationType
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
C.
featuresCompositionBy
Indicates that something includes or presents a composition created by a particular composer or creator.
-
D.
featureSet
chosen
Indicates that one entity is a collection or configuration of features associated with or applied to another entity.
-
E.
compositionalFeature
Indicates that one entity is a structural or constituent feature that forms part of the composition or makeup of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.