Triple

T16972912
Position Surface form Disambiguated ID Type / Status
Subject Madrid metropolitan area E411731 entity
Predicate hasRingRoad P9042 FINISHED
Object M-50 E448052 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: M-50 | Statement: [Madrid metropolitan area, hasRingRoad, M-50]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-50
Context triple: [Madrid metropolitan area, hasRingRoad, M-50]
  • A. M-50
    M-50 is a state trunkline highway in Michigan that runs east–west across the southern part of the state, connecting several communities and major routes.
  • B. M-50 chosen
    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-55
    M-55 is a state trunkline highway in Michigan that runs east–west across the northern Lower Peninsula, connecting several communities including the city of Manistee.
  • E. M-52
    M-52 is a state highway in Michigan that runs north–south through several counties, serving as an important regional route for local and through traffic.
  • 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_69d886ca8f348190812768ea8d5055ce completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d0ae47f08190a13e98d20aba7f16 completed April 18, 2026, 6:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b3f751c81908906ec969bef55c5 completed May 10, 2026, 11:56 p.m.
Created at: April 10, 2026, 5:31 a.m.