Triple
T13710404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warren County, Mississippi |
E328754
|
entity |
| Predicate | borderTypeWithMississippiRiver |
P75268
|
FINISHED |
| Object | western border |
—
|
LITERAL FINISHED |
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: western border | Statement: [Warren County, Mississippi, borderTypeWithMississippiRiver, western border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderTypeWithMississippiRiver Context triple: [Warren County, Mississippi, borderTypeWithMississippiRiver, western border]
-
A.
borderTypeWithTennessee
Indicates the specific type or nature of the border relationship an entity has with the state of Tennessee.
-
B.
USStateBorderFor
Indicates that a U.S. state serves as a bordering state for the specified geographic or political entity.
-
C.
borderRiverContext
chosen
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
-
D.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43949e6c8190ae5e4fa119cde33a |
completed | April 13, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.