Triple

T13415818
Position Surface form Disambiguated ID Type / Status
Subject Arkansas Highway 12 E313210 entity
Predicate hasJunctionWith P1018 FINISHED
Object U.S. Route 71B
U.S. Route 71B is a business route of U.S. Highway 71 that serves as a local arterial roadway through several cities in Arkansas, providing access to downtown and commercial areas.
E2289618 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: U.S. Route 71B | Statement: [Arkansas Highway 12, hasJunctionWith, U.S. Route 71B]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: U.S. Route 71B
Triple: [Arkansas Highway 12, hasJunctionWith, U.S. Route 71B]
Generated description
U.S. Route 71B is a business route of U.S. Highway 71 that serves as a local arterial roadway through several cities in Arkansas, providing access to downtown and commercial areas.

Provenance (5 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb6e904819098cc9153fd2feaf5 completed April 12, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b59a1d8dc8190b7ec77b3575e647b completed July 18, 2026, 10:46 a.m.
NEDg Description generation batch_6a5b59f6f1cc81908e0f793b5191dcbd completed July 18, 2026, 10:48 a.m.
NED2 Entity disambiguation (via description) batch_6a5b5a6fccbc8190bbab078f0eae0d8e completed July 18, 2026, 10:50 a.m.
Created at: April 9, 2026, 9:39 p.m.