Triple

T8386945
Position Surface form Disambiguated ID Type / Status
Subject Paracuellos de Jarama E197838 entity
Predicate hasRoadConnection P385 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: [Paracuellos de Jarama, hasRoadConnection, M-50]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-50
Context triple: [Paracuellos de Jarama, hasRoadConnection, M-50]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. M-59
    M-59 is an east–west state highway in southeastern Michigan that serves as a major suburban arterial route connecting communities north of Detroit.
  • E. 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.
  • 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_69ca82f749388190bffbea6dfb509016 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb81076eac8190893813628cacc1aa completed March 31, 2026, 8:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69cde83aac448190b74f65507170a8f7 completed April 2, 2026, 3:53 a.m.
Created at: March 30, 2026, 6:03 p.m.