Triple
T4664599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandu |
E102813
|
entity |
| Predicate | hasWaterBodies |
P19308
|
FINISHED |
| Object | artificial lakes |
—
|
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: artificial lakes | Statement: [Mandu, hasWaterBodies, artificial lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaterBodies Context triple: [Mandu, hasWaterBodies, artificial lakes]
-
A.
hasAreaWaterBody
chosen
Indicates that an entity includes, contains, or is associated with a body of water within its area or boundaries.
-
B.
focusesOnWaterBodies
Indicates a relationship where the subject’s attention, activity, or primary concern is directed toward water bodies such as lakes, rivers, or oceans.
-
C.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
D.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
E.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.