Triple
T4775882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadway Local |
E106044
|
entity |
| Predicate | trackTypeInManhattan |
P3832
|
FINISHED |
| Object | local tracks |
—
|
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: local tracks | Statement: [Broadway Local, trackTypeInManhattan, local tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trackTypeInManhattan Context triple: [Broadway Local, trackTypeInManhattan, local tracks]
-
A.
manhattanBridgeTrack
Indicates a connection or route that follows or uses the Manhattan Bridge as its primary path or segment.
-
B.
manhattanConnection
Indicates a direct or indirect connection or route between two entities specifically within the Manhattan area or grid.
-
C.
manhattanTrunkLine
Indicates a primary or central route, pathway, or connection running through a dense or core area, analogous to a main trunk line in Manhattan.
-
D.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
E.
onSideOfManhattan
Indicates that one entity is located on the same side of Manhattan as, or relative to, another reference entity.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.