Triple
T24127063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle County, Kentucky |
E597830
|
entity |
| Predicate | isOnMajorRiverSystem |
P124776
|
FINISHED |
| Object | Mississippi River Basin |
—
|
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: Mississippi River Basin | Statement: [Carlisle County, Kentucky, isOnMajorRiverSystem, Mississippi River Basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnMajorRiverSystem Context triple: [Carlisle County, Kentucky, isOnMajorRiverSystem, Mississippi River Basin]
-
A.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
B.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
C.
hasMajorHydroSystem
chosen
Indicates that an entity possesses or is associated with a primary or significant hydrological system, such as a major river, watershed, or water network.
-
D.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
E.
hasMajorCityOnBasin
Indicates that a major city is located on or within the drainage basin of a specified water system.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df740a508190a80af01d99000127 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:19 p.m.