Triple
T12765536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peyrou Promenade |
E305112
|
entity |
| Predicate | waterTowerFunction |
P106789
|
FINISHED |
| Object | terminal reservoir of the Saint-Clément aqueduct |
—
|
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: terminal reservoir of the Saint-Clément aqueduct | Statement: [Peyrou Promenade, waterTowerFunction, terminal reservoir of the Saint-Clément aqueduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTowerFunction Context triple: [Peyrou Promenade, waterTowerFunction, terminal reservoir of the Saint-Clément aqueduct]
-
A.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
B.
waterfallHeight
Indicates the vertical distance or drop in elevation from the top to the bottom of a waterfall.
-
C.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
D.
timeballTowerFunction
Indicates that something serves the function or role of a time ball tower, typically used to signal standardized time visually.
-
E.
waterInput
Indicates that an entity receives or is supplied with water from another source or system.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96df1ef148190af525532fcb0933b |
completed | April 10, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.