Triple
T19555677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enguri Dam |
E489302
|
entity |
| Predicate | hasMaintenanceProjects |
P103850
|
FINISHED |
| Object | EU- and EBRD-supported rehabilitation works |
—
|
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: EU- and EBRD-supported rehabilitation works | Statement: [Enguri Dam, hasMaintenanceProjects, EU- and EBRD-supported rehabilitation works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaintenanceProjects Context triple: [Enguri Dam, hasMaintenanceProjects, EU- and EBRD-supported rehabilitation works]
-
A.
hasMaintenanceProjectsBy
chosen
Indicates that one entity is responsible for or associated with carrying out maintenance projects on another entity.
-
B.
hasPlannedProjects
Indicates that an entity is associated with projects that are intended or scheduled to be carried out in the future.
-
C.
hasMaintenance
Indicates that an entity is subject to, associated with, or requires a particular maintenance activity or maintenance record.
-
D.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
E.
hasMaintenanceService
Indicates that an entity receives or is covered by a maintenance service provided by 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d335f888190abfc5ba974d3c65e |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.