Triple
T5648352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Texas |
E124438
|
entity |
| Predicate | operatingDirectionDuringChase |
P11673
|
FINISHED |
| Object | ran in reverse during much of the pursuit |
—
|
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: ran in reverse during much of the pursuit | Statement: [The Texas, operatingDirectionDuringChase, ran in reverse during much of the pursuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingDirectionDuringChase Context triple: [The Texas, operatingDirectionDuringChase, ran in reverse during much of the pursuit]
-
A.
raceDirection
Indicates the directional orientation or path along which a race or racing event proceeds.
-
B.
runsDirection
chosen
Indicates that an entity moves or operates in a specified direction.
-
C.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
crossingDirection
Indicates the direction in which one entity moves or passes across another reference point, boundary, or path.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d1534c8190ac4828e44300fb91 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.