Triple
T12526161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Stand |
E299445
|
entity |
| Predicate | heightAdjustmentRange |
P52251
|
FINISHED |
| Object | approximately 120 mm |
—
|
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: approximately 120 mm | Statement: [Pro Stand, heightAdjustmentRange, approximately 120 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightAdjustmentRange Context triple: [Pro Stand, heightAdjustmentRange, approximately 120 mm]
-
A.
displacementRange
chosen
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
B.
heightContext
Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
-
C.
weightRangeDescription
Indicates the textual description that specifies the range within which an entity’s weight falls.
-
D.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
E.
verticalExtent
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d9540d7b788190a0d57b098e90e491 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.