Triple
T30328602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 281 |
E771408
|
entity |
| Predicate | stateOfSouthernTerminus |
P51586
|
FINISHED |
| Object | Texas |
—
|
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: Texas | Statement: [U.S. Route 281, stateOfSouthernTerminus, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOfSouthernTerminus Context triple: [U.S. Route 281, stateOfSouthernTerminus, Texas]
-
A.
hasSouthernTerminus
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
-
B.
southernTerminusVariant
Indicates a variant or alternative form of the southern endpoint or terminus of something (such as a route, line, or boundary).
-
C.
southTerminusRegion
chosen
Indicates that a given region serves as the southern endpoint or terminus of a specified route, feature, or entity.
-
D.
southernTerminusCountry
Indicates the country in which the southern endpoint or terminus of something (such as a route, line, or feature) is located.
-
E.
southTerminusType
Indicates the type or nature of the southern endpoint or terminus of something (such as a route, line, or boundary).
- F. None of above.
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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: April 29, 2026, 7:53 p.m.