Triple
T3011718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | მტკვარი |
E82235
|
entity |
| Predicate | ჰიდროტექნიკური_ნაგებობა |
P4103
|
FINISHED |
| Object | მინგეჩაურის წყალსაცავი |
—
|
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: მინგეჩაურის წყალსაცავი | Statement: [მტკვარი, ჰიდროტექნიკური_ნაგებობა, მინგეჩაურის წყალსაცავი]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ჰიდროტექნიკური_ნაგებობა Context triple: [მტკვარი, ჰიდროტექნიკური_ნაგებობა, მინგეჩაურის წყალსაცავი]
-
A.
waterInfrastructure
chosen
Indicates the existence, development, or management of systems and facilities that supply, store, treat, or distribute water between entities.
-
B.
hasHydroelectricProject
Indicates that an entity is associated with, operates, or contains a hydroelectric power generation project.
-
C.
hydrology
Indicates the relationship between entities and the movement, distribution, or properties of water within natural or engineered environments.
-
D.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
-
E.
hasStructureOnWatercourse
Indicates that a structure is physically located on, over, or directly associated with a specific watercourse.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a66c334819082d1d320c48eca1b |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad961a97188190809dc73430a8eda8 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.