Triple
T9908675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pullinque Lake |
E185082
|
entity |
| Predicate | hasHydrologicalInflow |
P36348
|
FINISHED |
| Object | Enco River |
—
|
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: Enco River | Statement: [Pullinque Lake, hasHydrologicalInflow, Enco River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHydrologicalInflow Context triple: [Pullinque Lake, hasHydrologicalInflow, Enco River]
-
A.
inflowWatercourse
chosen
Indicates that one watercourse flows into or feeds another water body or watercourse.
-
B.
hasHydrologicalRegime
Indicates that one entity (typically a water body or hydrological system) is characterized by, or associated with, a particular pattern or regime of water flow and levels over time.
-
C.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
D.
hasHydrologicalRelation
Indicates a relationship between entities based on the movement, distribution, or connection of water within or between hydrological features or systems.
-
E.
hasBodyOfWaterDrainedBy
Indicates that a body of water is emptied or its water flow is carried away by a specified draining feature, such as a river, channel, or drainage 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb50feb008190aa9c084f590c0ebd |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.