Triple
T17423456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPI F40PH-3C |
E423675
|
entity |
| Predicate | hasControlStand |
P6313
|
FINISHED |
| Object | desktop control stand |
—
|
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: desktop control stand | Statement: [MPI F40PH-3C, hasControlStand, desktop control stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlStand Context triple: [MPI F40PH-3C, hasControlStand, desktop control stand]
-
A.
hasStand
chosen
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
B.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
C.
hasStandsType
Indicates that an entity has or is associated with a particular type or category of stands (e.g., display stands, support stands, or similar structures).
-
D.
hasPhysicalControl
Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
-
E.
hasMainStandOn
Indicates that one entity serves as the primary physical support structure or main stand for 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44238b418819095c6a013d3ff3b17 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.