Triple
T31938374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greer County, Texas (historical) |
E815455
|
entity |
| Predicate | borderDisputeInvolvedRiver |
P93095
|
FINISHED |
| Object | Red River |
—
|
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: Red River | Statement: [Greer County, Texas (historical), borderDisputeInvolvedRiver, Red River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeInvolvedRiver Context triple: [Greer County, Texas (historical), borderDisputeInvolvedRiver, Red River]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
C.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
D.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
E.
transboundaryRiverOf
chosen
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: May 1, 2026, 12:05 a.m.