Triple
T17080559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reactor No. 4 |
E414457
|
entity |
| Predicate | containmentStructure |
P125792
|
FINISHED |
| Object | no full Western-style containment building |
—
|
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: no full Western-style containment building | Statement: [Reactor No. 4, containmentStructure, no full Western-style containment building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containmentStructure Context triple: [Reactor No. 4, containmentStructure, no full Western-style containment building]
-
A.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
B.
requiresContainment
Indicates that one entity must be physically or logically enclosed within another entity as a necessary condition or constraint.
-
C.
containerType
Indicates the specific kind or category of container associated with or used to hold an entity.
-
D.
internalStructure
Indicates that one entity is a component, part, or substructure contained within the overall structure of another entity.
-
E.
containsStructureFrom
Indicates that one entity includes or incorporates a structural component originating from another entity.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe24a6481908b4596c95220df4a |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:34 a.m.