Triple
T17754349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transit America |
E443193
|
entity |
| Predicate | vehicleLocation |
P81157
|
FINISHED |
| Object | Chicago, Illinois (in service) |
—
|
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: Chicago, Illinois (in service) | Statement: [Transit America, vehicleLocation, Chicago, Illinois (in service)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleLocation Context triple: [Transit America, vehicleLocation, Chicago, Illinois (in service)]
-
A.
tracksLocation
Indicates that one entity monitors and records the geographic position or movement of another entity over time.
-
B.
locationNowCalled
Indicates that a location is currently known or referred to by a different (typically newer) name than it was previously.
-
C.
locationDuringUse
chosen
Indicates the place or spatial context where an entity is situated specifically while it is being used or in active operation.
-
D.
currentLocationType
Indicates the type or category of place where an entity is currently located.
-
E.
currentLocationSince
Indicates the point in time since which an entity has been at its current location.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841da9988190b5efde3bbd3f24c3 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.