Triple
T840624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interborough Rapid Transit Company |
E18167
|
entity |
| Predicate | firstSubwayOpeningDate |
P20538
|
FINISHED |
| Object | 1904-10-27 |
—
|
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: 1904-10-27 | Statement: [Interborough Rapid Transit Company, firstSubwayOpeningDate, 1904-10-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSubwayOpeningDate Context triple: [Interborough Rapid Transit Company, firstSubwayOpeningDate, 1904-10-27]
-
A.
metroLineInaugurated
Indicates that a metro line was officially opened and began operation on a specific date or during a specific event.
-
B.
railwayStationOpened
Indicates that a railway station began operation or was officially opened on a specified date or in a specified time period.
-
C.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
D.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
E.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
- F. None of above. chosen
Provenance (4 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe5d7848190b15e0cb343b6f4ba |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.