Triple
T1134737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Avenue Line |
E23112
|
entity |
| Predicate | northSouthCorridor |
P21550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Lexington Avenue Line, northSouthCorridor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northSouthCorridor Context triple: [Lexington Avenue Line, northSouthCorridor, yes]
-
A.
northSouthRoutes
chosen
Indicates that there are routes or connections running in a generally north–south direction between the related entities.
-
B.
Purple Line Express
Indicates a transportation service or route designated as the "Purple Line" that operates with express (limited-stop) service between locations.
-
C.
northSection
Indicates that one entity is located in, belongs to, or corresponds to the northern section or northern part of another entity.
-
D.
majorUrbanCorridor
Indicates a primary transportation route that connects significant urban areas and supports major flows of people, goods, or services between them.
-
E.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bde18d208190848c189b2b8d585f |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4b52d48190bec2e7ad1cc8efc0 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.