Triple
T20454410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loop 323 (Tyler) |
E501736
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | Loop 323 |
—
|
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: Loop 323 | Statement: [Loop 323 (Tyler), abbreviation, Loop 323]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loop 323 Context triple: [Loop 323 (Tyler), abbreviation, Loop 323]
-
A.
Loop 323
chosen
Loop 323 is a primary circumferential highway that serves as the main loop route around the city of Tyler, Texas.
-
B.
Loop 336
Loop 336 is a major circumferential roadway that serves as a key traffic artery around the city of Conroe, Texas.
-
C.
Loop 303
Loop 303 is a major freeway in the Phoenix metropolitan area that serves as part of the region’s outer beltway system, facilitating circumferential travel and suburban growth.
-
D.
Loop 286
Loop 286 is a state highway loop that serves as a beltway around the city of Paris in Lamar County, Texas.
-
E.
Loop 1604
Loop 1604 is a major highway encircling much of San Antonio, Texas, serving as a key route for regional traffic and access to suburban districts and commercial areas.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e68d04ca4081909b428c31d16fca10 |
completed | April 20, 2026, 8:31 p.m. |
Created at: April 16, 2026, 11:32 a.m.