Triple
T9673213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sellafield |
E234080
|
entity |
| Predicate | hasReprocessingActivity |
P89553
|
FINISHED |
| Object | Magnox fuel |
—
|
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: Magnox fuel | Statement: [Sellafield, hasReprocessingActivity, Magnox fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReprocessingActivity Context triple: [Sellafield, hasReprocessingActivity, Magnox fuel]
-
A.
hasOngoing
Indicates that one entity is currently engaged in, experiencing, or maintaining an activity, state, or process that has not yet concluded.
-
B.
hasActivityCycle
Indicates that an entity exhibits a recurring pattern or cycle of activity over time.
-
C.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
D.
hasRestorationActivities
Indicates that an entity carries out, is involved in, or is associated with actions aimed at restoring or rehabilitating another entity or resource.
-
E.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6c05c481909885bfdb850e7527 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:15 p.m.