Triple

T21542049
Position Surface form Disambiguated ID Type / Status
Subject 10 Loop E531515 entity
Predicate alsoKnownAs P39 FINISHED
Object SR 10 Loop 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: SR 10 Loop | Statement: [10 Loop, alsoKnownAs, SR 10 Loop]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SR 10 Loop
Context triple: [10 Loop, alsoKnownAs, SR 10 Loop]
  • A. SR 10 Loop chosen
    SR 10 Loop is a state highway bypass encircling Athens, Georgia, providing a major route for local and through traffic around the city.
  • B. SR 103
    SR 103 is a state highway on Washington’s Long Beach Peninsula that serves as a primary north–south route connecting coastal communities and recreational areas.
  • C. SR 109
    SR 109 is a state highway in Maine that connects the coastal city of Wells with inland communities, serving as a regional route for local and through traffic.
  • D. SR 193
    SR 193 is a Virginia state highway known as Georgetown Pike, a historic and scenic road in Northern Virginia.
  • E. SR 193
    SR 193 is a state highway in Maine that connects the communities of Cherryfield and Beddington in Washington County.
  • 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_69e0c45f17148190949c330ab9c27706 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeb58c34808190b0eb54ba01e2cc13 completed April 27, 2026, 1:02 a.m.
Created at: April 16, 2026, 6:28 p.m.