Triple
T2261153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyckman Street (A line) |
E50041
|
entity |
| Predicate | division |
P889
|
FINISHED |
| Object | IND |
E79364
|
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: IND | Statement: [Dyckman Street (A line), division, IND]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IND Context triple: [Dyckman Street (A line), division, IND]
-
A.
IND
IND is the abbreviated name commonly used for the Industriales baseball team, one of the most popular and successful clubs in Cuban baseball.
-
B.
IND
chosen
IND (Independent Subway System) was New York City's municipally built and operated subway network that later became one of the three major divisions of the unified NYC Subway.
-
C.
IN
IN is the two-letter ISO 3166-1 alpha-2 country code representing India in international standards and systems.
-
D.
IN
IN is the official two-letter United States Postal Service abbreviation for the state of Indiana.
-
E.
Indi
Indi is an Australian federal electoral division in the state of Victoria, encompassing a largely rural and regional area in the state's northeast.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc18aa9d48190893ca32558730e9c |
completed | March 7, 2026, 6:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71cb1540819093db7f91ae66c19f |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:48 p.m.