Triple
T7769419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky and Missouri |
E179031
|
entity |
| Predicate | shareTypeOfBoundary |
P35564
|
FINISHED |
| Object | fluvial boundary |
—
|
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: fluvial boundary | Statement: [Kentucky and Missouri, shareTypeOfBoundary, fluvial boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareTypeOfBoundary Context triple: [Kentucky and Missouri, shareTypeOfBoundary, fluvial boundary]
-
A.
shareNotableBorderRegion
Indicates that two entities share a common border in a region that is particularly significant or notable (e.g., historically, politically, or geographically).
-
B.
sharesBorderingNetworkWith
Indicates that two entities are connected through adjacent or directly neighboring positions within the same network structure.
-
C.
sharesBorderType
chosen
Indicates that two entities are connected by a common boundary characterized by the same specified type of border (e.g., land, river, maritime).
-
D.
sharesBayWith
Indicates that two locations are situated along or adjacent to the same bay.
-
E.
shareWaterBoundary
Indicates that two entities are adjacent to each other with a shared boundary formed by a body of water.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c704376dc08190890f5ebb9f259cfd |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.