Triple
T7374587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 53rd Street Tunnel |
E170091
|
entity |
| Predicate | carriedLines |
P51670
|
FINISHED |
| Object | E 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: E service | Statement: [53rd Street Tunnel, carriedLines, E service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedLines Context triple: [53rd Street Tunnel, carriedLines, E service]
-
A.
carriedByLine
chosen
Indicates that something (such as a service, signal, or connection) is transported or conveyed via a particular line or conduit.
-
B.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
C.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
D.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
-
E.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
- 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1a6643c81909d626c8b6a7a11fd |
completed | March 27, 2026, 9:07 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:07 p.m.