Triple
T34147831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Île de la Motte |
E875910
|
entity |
| Predicate | locatedInReservoir |
P205338
|
FINISHED |
| Object | Lake of Gruyère |
E249888
|
NE 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: Lake of Gruyère | Statement: [Île de la Motte, locatedInReservoir, Lake of Gruyère]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInReservoir Context triple: [Île de la Motte, locatedInReservoir, Lake of Gruyère]
-
A.
reservoirLocation
Indicates that a reservoir is geographically located at or within a specified place or region.
-
B.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
C.
reservoirAlsoKnownAs
Indicates that a reservoir is referred to by an alternative name or alias.
-
D.
hasReservoirOnTributary
Indicates that a reservoir is located on a tributary of a main water body rather than on the main water body itself.
-
E.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
- F. None of above. chosen
Provenance (5 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3752d03d0481908aba37f842e52532 |
completed | June 21, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:54 a.m.