Triple
T6221464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churchill Falls Generating Station |
E139123
|
entity |
| Predicate | undergroundCavernWidth |
P68980
|
FINISHED |
| Object | about 25 metres |
—
|
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 25 metres | Statement: [Churchill Falls Generating Station, undergroundCavernWidth, about 25 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undergroundCavernWidth Context triple: [Churchill Falls Generating Station, undergroundCavernWidth, about 25 metres]
-
A.
caveType
Indicates the specific classification or kind of cave associated with an entity.
-
B.
caveNumber
Indicates a relationship where an entity is assigned or associated with a specific cave identifier or number.
-
C.
hasCaves
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
D.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
E.
hasUndergroundCellarsLength
Indicates that an entity possesses underground cellars whose length is specified or measured.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bcc2348190806ed8c98bdfbf3e |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:22 p.m.