Triple

T7500176
Position Surface form Disambiguated ID Type / Status
Subject MD 500 E177235 entity
Predicate variant P4680 FINISHED
Object MD 500D E177235 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: MD 500D | Statement: [MD 500, variant, MD 500D]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MD 500D
Context triple: [MD 500, variant, MD 500D]
  • A. MD 500 chosen
    The MD 500 is a family of light, single-engine civilian and military helicopters known for their agility, compact size, and use in roles ranging from transport to law enforcement and special operations.
  • B. M-50
    M-50 is a major orbital motorway around Madrid, Spain, designed to divert traffic from the city center and connect key suburbs and highways.
  • C. M-5
    M-5 is a state highway in southeastern Michigan that serves as a key commuter route connecting Novi and surrounding suburbs to the Detroit metropolitan area.
  • D. M-506
    M-506 is a regional road in the Community of Madrid, Spain, that serves as a key connector for the municipality of Pinto and surrounding areas.
  • E. ND-500
    ND-500 was a line of 32-bit minicomputers produced by Norwegian computer manufacturer Norsk Data, used primarily for scientific, technical, and real-time applications in the 1970s and 1980s.
  • 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_69c69f2696688190915a8458f2398211 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f598dfac8190a123daaac0784aee completed March 27, 2026, 9:24 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83c900ad081908506a2097f7fd30b completed March 28, 2026, 8:39 p.m.
Created at: March 27, 2026, 3:44 p.m.