Triple
T35999510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabeglavi village bottling plant |
E1041089
|
entity |
| Predicate | locatedOnWaterType |
P207126
|
FINISHED |
| Object | mineral water source |
—
|
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: mineral water source | Statement: [Nabeglavi village bottling plant, locatedOnWaterType, mineral water source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnWaterType Context triple: [Nabeglavi village bottling plant, locatedOnWaterType, mineral water source]
-
A.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
B.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
C.
hostedOnWaterBodyType
Indicates that an event, activity, or entity takes place on or is situated upon a specific type of water body (e.g., lake, river, ocean).
-
D.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
E.
hasBodyOfWaterType
Indicates that a body of water is classified as being of a particular type or category (such as lake, river, ocean, etc.).
- F. None of above. chosen
Provenance (4 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.