Triple
T13426062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rally Car |
E313484
|
entity |
| Predicate | displacementLimit |
P84064
|
FINISHED |
| Object | 2.0-litre (pre-2011 era) |
—
|
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: 2.0-litre (pre-2011 era) | Statement: [World Rally Car, displacementLimit, 2.0-litre (pre-2011 era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displacementLimit Context triple: [World Rally Car, displacementLimit, 2.0-litre (pre-2011 era)]
-
A.
hasMaxDisplacement
chosen
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
-
B.
displacementRate
Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
-
C.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
D.
treatyDisplacementLimit
Indicates that a treaty specifies a maximum allowable level or extent of displacement resulting from actions governed by that agreement.
-
E.
displacementPeriod
Indicates the time interval over which an entity is moved or shifted from one position or state to another.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.