Triple
T28884458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aqueduct of Maintenon |
E732515
|
entity |
| Predicate | waterSourceIntended |
P4102
|
FINISHED |
| Object | Eure River |
—
|
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: Eure River | Statement: [Aqueduct of Maintenon, waterSourceIntended, Eure River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSourceIntended Context triple: [Aqueduct of Maintenon, waterSourceIntended, Eure River]
-
A.
waterSource
chosen
Indicates that one entity serves as the source or provider of water for another entity.
-
B.
waterSourceDedicatedTo
Indicates that a particular water source is specifically allocated or reserved for a designated use, group, or purpose.
-
C.
waterSourceAfter
Indicates that one water source occurs, appears, or is accessed after another in time or sequence.
-
D.
waterSourceType
Indicates the kind or category of source from which water is obtained.
-
E.
waterSourceContext
Indicates the contextual relationship between a water source and the conditions, setting, or circumstances under which it is used, accessed, or relevant.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 7:48 a.m.