Triple
T24155819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neosho, Missouri |
E598674
|
entity |
| Predicate | waterFeatures |
P64067
|
FINISHED |
| Object | springs and small streams in and around the city |
—
|
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: springs and small streams in and around the city | Statement: [Neosho, Missouri, waterFeatures, springs and small streams in and around the city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterFeatures Context triple: [Neosho, Missouri, waterFeatures, springs and small streams in and around the city]
-
A.
waterFeature
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
B.
hasWaterFeatures
chosen
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
C.
waterSource
Indicates that one entity serves as the source or provider of water for another entity.
-
D.
hasWaterCharacteristics
Indicates that one entity possesses qualities, properties, or behaviors characteristic of water.
-
E.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e4fc9c8190bafabb4f08a2db45 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:31 p.m.