Triple
T15378431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ctalamochita River |
E367732
|
entity |
| Predicate | watercourseFunction |
P80269
|
FINISHED |
| Object | drainage of central Córdoba Province |
—
|
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: drainage of central Córdoba Province | Statement: [Ctalamochita River, watercourseFunction, drainage of central Córdoba Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseFunction Context triple: [Ctalamochita River, watercourseFunction, drainage of central Córdoba Province]
-
A.
watercourseFor
chosen
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
B.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
-
C.
watercourseProgression
Indicates the downstream sequence in which a watercourse flows into other water bodies or watercourses.
-
D.
watercourseName
Indicates the name assigned to a river, stream, or other flowing body of water in the relationship.
-
E.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e6044488190b0499db109f7f821 |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.