Triple
T14365420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooklyn IRT lines |
E356218
|
entity |
| Predicate | systemStyle |
P13268
|
FINISHED |
| Object | IRT |
E63229
|
NE 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: IRT | Statement: [Brooklyn IRT lines, systemStyle, IRT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IRT Context triple: [Brooklyn IRT lines, systemStyle, IRT]
-
A.
IRT
chosen
IRT is a major division of the New York City Subway system that operates the numbered (1–7) train lines, originally built by the Interborough Rapid Transit Company.
-
B.
IR
IR is the IATA airline designator assigned to Iran Air, the national flag carrier of Iran.
-
C.
IR
IR is the branding abbreviation used for InterRegio, a category of medium- to long-distance passenger trains operating in several European countries.
-
D.
IR
IR is the ISO 3166-1 alpha-2 country code for Iran, a large Middle Eastern nation known for its ancient Persian heritage and significant geopolitical influence.
-
E.
IRE
IRE is the three-letter World Rugby code representing the Ireland national rugby union team.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fad48748190a0f34ca4d02f9a3c |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c4fa3788190b7fa5c34620c3ada |
completed | May 8, 2026, 2:37 a.m. |
Created at: April 10, 2026, 1:15 a.m.