Triple

T21383396
Position Surface form Disambiguated ID Type / Status
Subject 190th Street E527423 entity
Predicate division P889 FINISHED
Object IND NE NERFINISHED

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: [190th Street, division, IND]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IND
Context triple: [190th Street, division, 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 standard international abbreviation used to represent the India national cricket team in scorecards, rankings, and official records.
  • E. IND
    IND is the acronym for the Instituto Nicaragüense de Deportes, Nicaragua’s national government body responsible for promoting and regulating sports in the country.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b51f363c8190944000ab5523b02b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8b0f05278819096c511035ffc9777 completed April 22, 2026, 11:28 a.m.
Created at: April 16, 2026, 5:12 p.m.