Triple
T10749486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Llyn Trawsfynydd |
E253535
|
entity |
| Predicate | primaryPurposeOriginal |
P75472
|
FINISHED |
| Object | cooling water supply |
—
|
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: cooling water supply | Statement: [Llyn Trawsfynydd, primaryPurposeOriginal, cooling water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPurposeOriginal Context triple: [Llyn Trawsfynydd, primaryPurposeOriginal, cooling water supply]
-
A.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
B.
originalPrimaryUse
chosen
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
-
C.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
D.
primarySignificance
Indicates that something has the greatest importance, relevance, or impact among a set of related things or factors.
-
E.
primarilyFor
Indicates that something is mainly intended, designed, or used for a particular purpose, function, or beneficiary, even if it may have secondary uses.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d71dbecd58819081e859ebf72f656c |
completed | April 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.