Triple
T27488657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iskar Reservoir |
E693815
|
entity |
| Predicate | isLargestReservoirNear |
P162439
|
FINISHED |
| Object | Sofia |
—
|
NE NERFINISHED |
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: Sofia | Statement: [Iskar Reservoir, isLargestReservoirNear, Sofia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestReservoirNear Context triple: [Iskar Reservoir, isLargestReservoirNear, Sofia]
-
A.
isLargestReservoirIn
Indicates that one entity is the largest reservoir located within or associated with another entity (such as a region, river system, or administrative area).
-
B.
nearestLargeReservoir
Indicates that one entity is the closest large reservoir in distance to the other entity.
-
C.
isThirdLargestReservoirIn
Indicates that a reservoir is the third largest (by capacity or area) among all reservoirs within a specified region or jurisdiction.
-
D.
nearestLargeLake
Indicates that one entity is the closest large lake in distance to the other entity.
-
E.
isLargestInlandLakeIn
Indicates that a lake is the largest inland lake within the specified geographic region or area.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8720a481908e9bc6e74631df4b |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:04 p.m.