Triple
T34451825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnox Ltd |
E884388
|
entity |
| Predicate | typeOfSitePortfolio |
P15047
|
FINISHED |
| Object | first-generation gas-cooled reactors |
—
|
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: first-generation gas-cooled reactors | Statement: [Magnox Ltd, typeOfSitePortfolio, first-generation gas-cooled reactors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSitePortfolio Context triple: [Magnox Ltd, typeOfSitePortfolio, first-generation gas-cooled reactors]
-
A.
typeOfSite
chosen
Indicates the specific category or kind of site that an entity is classified as.
-
B.
portfolioOf
Indicates that one entity is the collection of investments, works, or assets that are owned, managed, or represented by another entity.
-
C.
typicalPortfolio
Indicates that one entity is the standard or representative portfolio associated with another entity (such as a person, account, or organization).
-
D.
typeSite
Indicates that a site is classified as being of a particular type or category.
-
E.
portfolioAgency
Indicates that one entity serves as the managing or representative agency responsible for overseeing or administering another entity’s portfolio.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a013a251b4081908b43d85dd95586c5 |
completed | May 11, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a0137e4ea988190812173a5ff044098 |
completed | May 11, 2026, 1:59 a.m. |
Created at: May 1, 2026, 2 a.m.