Triple
T7959274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodowa |
E184819
|
entity |
| Predicate | waterBodyFeature |
P31054
|
FINISHED |
| Object | waterfalls |
—
|
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: waterfalls | Statement: [Dodowa, waterBodyFeature, waterfalls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyFeature Context triple: [Dodowa, waterBodyFeature, waterfalls]
-
A.
hasWaterBodyCharacteristic
Indicates that a water body possesses a specified physical, chemical, or ecological characteristic.
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
D.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
E.
hydrologyFeature
chosen
Indicates a relationship where one entity is a hydrological feature (such as a body or flow of water) associated with or characterizing another entity.
- 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_69ca8293a2388190aace944d7ed9c0c0 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b80050c81909b2db95ade495052 |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:11 p.m.