Triple
T33042571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elan Aqueduct |
E845506
|
entity |
| Predicate | dailyCapacity |
P175733
|
FINISHED |
| Object | about 300 million litres |
—
|
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: about 300 million litres | Statement: [Elan Aqueduct, dailyCapacity, about 300 million litres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyCapacity Context triple: [Elan Aqueduct, dailyCapacity, about 300 million litres]
-
A.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
-
B.
capacityPerHour
Indicates the maximum amount of output or throughput an entity can handle or produce in one hour.
-
C.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
D.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
E.
operatorCapacity
Indicates the maximum workload or volume of tasks that an operator is able to handle within a given context or time frame.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:24 a.m.