Triple
T3133671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Avenue–53rd Street |
E65476
|
entity |
| Predicate | hasDivision |
P35
|
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: [Lexington Avenue–53rd Street, hasDivision, IND]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IND Context triple: [Lexington Avenue–53rd Street, hasDivision, IND]
-
A.
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.
-
B.
IND
IND is the abbreviated name and common shorthand for the American professional soccer club Indy Eleven.
-
C.
IND
IND is the three-letter IATA airport code for Indianapolis International Airport, the primary commercial airport serving Indianapolis, Indiana.
-
D.
IND
IND is the abbreviated name commonly used for the Industriales baseball team, one of the most popular and successful clubs in Cuban baseball.
-
E.
IND
IND is the standard abbreviation used to represent the Indianapolis Jets sports 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada56104ec8190a14591ed73f3fe83 |
completed | March 8, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b24b39d40c8190a5b1a74cfa4caa81 |
completed | March 12, 2026, 5:12 a.m. |
Created at: March 8, 2026, 3:05 p.m.