Triple
T3737858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden Calais |
E79627
|
entity |
| Predicate | positionWithinRange |
P44324
|
FINISHED |
| Object | above standard Commodore variants |
—
|
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: above standard Commodore variants | Statement: [Holden Calais, positionWithinRange, above standard Commodore variants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionWithinRange Context triple: [Holden Calais, positionWithinRange, above standard Commodore variants]
-
A.
positionInRange
chosen
Indicates that an entity’s position lies within a specified numerical or spatial range.
-
B.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
C.
positionIncluded
Indicates that one position or spatial region is entirely contained within another position or spatial region.
-
D.
positionInBand
Indicates the specific role or place an individual holds within a musical band.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3e9248819098d481fe29e1c628 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.