Triple
T30312638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 281 |
E770968
|
entity |
| Predicate | southernTerminusCountryBorder |
P5249
|
FINISHED |
| Object | Mexico–United States border |
—
|
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: Mexico–United States border | Statement: [US 281, southernTerminusCountryBorder, Mexico–United States border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: southernTerminusCountryBorder Context triple: [US 281, southernTerminusCountryBorder, Mexico–United States border]
-
A.
southernTerminusCountry
Indicates the country in which the southern endpoint or terminus of something (such as a route, line, or feature) is located.
-
B.
easternTerminusCountry
Indicates the country in which the eastern terminus (end point) of something, such as a route or infrastructure, is located.
-
C.
hasSouthBorder
Indicates that one entity shares its southern boundary or border with another entity.
-
D.
boundaryTypeSouth
Indicates the type or nature of the boundary that lies to the south of a given entity.
-
E.
hasSouthernTerminus
chosen
Indicates that one entity serves as the southern endpoint or terminus of another entity, such as a route, line, or path.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816ceb688190b2e5f01205f3c550 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:50 p.m.