Triple
T24069306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twentysix Gasoline Stations |
E596180
|
entity |
| Predicate | routeCovered |
P152441
|
FINISHED |
| Object | Los Angeles to Oklahoma City |
—
|
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: Los Angeles to Oklahoma City | Statement: [Twentysix Gasoline Stations, routeCovered, Los Angeles to Oklahoma City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeCovered Context triple: [Twentysix Gasoline Stations, routeCovered, Los Angeles to Oklahoma City]
-
A.
routeCoverage
chosen
Indicates that one entity’s route or path sufficiently covers, serves, or includes the area, segments, or points associated with another entity.
-
B.
routeAlong
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by another entity.
-
C.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
-
D.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db15866c8190ab931216b8d9c57f |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.