Triple
T23965427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G14 (IND component) |
E604064
|
entity |
| Predicate | appliesToStationComplex |
P102516
|
FINISHED |
| Object | 74th Street–Broadway |
—
|
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: 74th Street–Broadway | Statement: [G14 (IND component), appliesToStationComplex, 74th Street–Broadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToStationComplex Context triple: [G14 (IND component), appliesToStationComplex, 74th Street–Broadway]
-
A.
appliesToTransitStation
chosen
Indicates that something (such as a rule, feature, condition, or attribute) is specifically relevant or applicable to a transit station.
-
B.
hasStationFunction
Indicates that an entity serves in a particular functional role or capacity at a station.
-
C.
hasComponentStation
Indicates that an entity includes or is associated with a specific station as one of its component parts.
-
D.
developedForStation
Indicates that something was specifically created or engineered to be used at or in connection with a particular station.
-
E.
hasStationAt
Indicates that an entity maintains or operates a station located at a specified place.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1d7077881909d4774b7040cd722 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:24 p.m.