Triple
T33516610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Del Rio–Ciudad Acuña International Bridge |
E858382
|
entity |
| Predicate | stateOnUSSide |
P43351
|
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: [Del Rio–Ciudad Acuña International Bridge, stateOnUSSide, Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateOnUSSide Context triple: [Del Rio–Ciudad Acuña International Bridge, stateOnUSSide, Texas]
-
A.
borderStateOnUSSide
chosen
Indicates that a state is located on the U.S. side of an international border shared with another country.
-
B.
stateEnsign
Indicates that an entity holds the naval rank or position of an ensign within a particular state or governmental context.
-
C.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
D.
governingBodySideUS
Indicates that the referenced entity serves as the U.S. side or participant in a governing or decision-making body shared with another party.
-
E.
usesState
Indicates that one entity operates with, depends on, or is configured to function using a particular state or condition of another entity.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:39 a.m.