Triple

T19820522
Position Surface form Disambiguated ID Type / Status
Subject M-300 road E476178 entity
Predicate hasRouteNumber P1864 FINISHED
Object M-300 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: M-300 | Statement: [M-300 road, hasRouteNumber, M-300]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: M-300
Context triple: [M-300 road, hasRouteNumber, M-300]
  • A. M-300 chosen
    M-300 is a regional road in the Community of Madrid, Spain, that connects several municipalities in the eastern part of the region.
  • B. M-30
    M-30 is a major orbital ring road encircling central Madrid and serving as one of the city’s primary traffic arteries.
  • C. M-600
    M-600 is a regional road in the Community of Madrid, Spain, that connects several towns including Brunete.
  • D. M-3
    M-3 is a designated highway route, commonly known by its short name M-3, within a regional or national road network.
  • E. M-35
    M-35 is a state trunkline highway in Michigan’s Upper Peninsula that runs along the shore of Green Bay and connects several communities in Menominee County and beyond.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654fe0ff8819084bad251b76eff77 completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.