Triple
T28021051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosstown Local |
E707687
|
entity |
| Predicate | hasRouteID |
P34375
|
FINISHED |
| Object | G |
—
|
NE NERFINISHED |
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: G | Statement: [Crosstown Local, hasRouteID, G]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteID Context triple: [Crosstown Local, hasRouteID, G]
-
A.
hasRouteIdentifier
chosen
Indicates that an entity is associated with a specific route code or identifier used to distinguish it from other routes.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
hasRouteNumberingRole
Indicates that an entity participates in the assignment, management, or designation of route numbers for a transportation route or network.
-
D.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
E.
hasRouteType
Indicates that there is a specific kind or category of route associated with an entity (e.g., road, rail, bus line).
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 8:10 p.m.