Triple
T34484342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnox |
E885275
|
entity |
| Predicate | typicalContainment |
P95472
|
FINISHED |
| Object | reactor building with biological shielding |
—
|
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: reactor building with biological shielding | Statement: [Magnox, typicalContainment, reactor building with biological shielding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalContainment Context triple: [Magnox, typicalContainment, reactor building with biological shielding]
-
A.
containment
Indicates that one entity is spatially or conceptually enclosed within the boundaries or scope of another entity.
-
B.
typicallyContain
chosen
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
-
C.
containmentStructure
Indicates that one entity serves as a physical or logical container or enclosing structure for another entity.
-
D.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
E.
requiresContainment
Indicates that one entity must be physically or logically enclosed within another entity as a necessary condition or constraint.
- 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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.