Triple
T2294265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trawsfynydd |
E51573
|
entity |
| Predicate | hasFormerIndustry |
P19843
|
FINISHED |
| Object | nuclear power generation |
—
|
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: nuclear power generation | Statement: [Trawsfynydd, hasFormerIndustry, nuclear power generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerIndustry Context triple: [Trawsfynydd, hasFormerIndustry, nuclear power generation]
-
A.
hasHistoricIndustry
Indicates that an entity has been associated with a notable or historically significant industry or industrial activity in the past.
-
B.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
D.
hasPrincipalIndustry
Indicates that an entity’s main or primary industry of operation is the specified industry.
-
E.
formerEconomicActivity
chosen
Indicates that an entity previously engaged in a specified economic activity but no longer does so.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abcd0e42248190ada33b84d75caa64 |
completed | March 7, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69abc589295c819092989820c2b4e9d8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.