Triple
T26278587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND Queens–Manhattan river crossings |
E660640
|
entity |
| Predicate | carriedLine |
P51670
|
FINISHED |
| Object | IND Queens Boulevard Line |
—
|
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: IND Queens Boulevard Line | Statement: [IND Queens–Manhattan river crossings, carriedLine, IND Queens Boulevard Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriedLine Context triple: [IND Queens–Manhattan river crossings, carriedLine, IND Queens Boulevard Line]
-
A.
carriedByLine
chosen
Indicates that something (such as a service, signal, or connection) is transported or conveyed via a particular line or conduit.
-
B.
carriedFor
Indicates that one entity transported or bore another entity on behalf of or for the benefit of that other entity.
-
C.
carriedTo
Indicates that one entity transported or conveyed another entity from one place to another.
-
D.
followedLineOf
Indicates that one entity moved along or traced the same path or trajectory previously taken or defined by another entity.
-
E.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 9:58 p.m.