Triple
T97689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT Division |
E1967
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | IRT |
E1967
|
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: [IRT Division, hasAbbreviation, IRT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IRT Context triple: [IRT Division, hasAbbreviation, IRT]
-
A.
IRT Division
chosen
The IRT Division is one of the original operating divisions of the New York City Subway, historically derived from the Interborough Rapid Transit Company and encompassing the system’s numbered subway lines.
-
B.
TR
TR is the two-letter ISO 3166-1 alpha-2 country code assigned to Turkey for international standardization and referencing.
-
C.
IMP
IMP is an early packet-switching node used in the ARPANET, serving as a precursor to modern internet routers.
-
D.
IN
IN is the two-letter ISO 3166-1 alpha-2 country code representing India in international standards and systems.
-
E.
IGWT
IGWT is the commonly used abbreviation for the phrase "In God We Trust," the official motto of the United States.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a284fd52f08190b264937658192e79 |
completed | Feb. 28, 2026, 6:02 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.