Triple
T4661674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States nuclear energy program |
E102546
|
entity |
| Predicate | usesReactorType |
P3675
|
FINISHED |
| Object | pressurized water reactor |
—
|
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: pressurized water reactor | Statement: [United States nuclear energy program, usesReactorType, pressurized water reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesReactorType Context triple: [United States nuclear energy program, usesReactorType, pressurized water reactor]
-
A.
hasReactorUnit
Indicates that one entity possesses, contains, or is equipped with a specific reactor unit as a component or subsystem.
-
B.
reactorType
chosen
Indicates the specific kind or category of reactor associated with an entity.
-
C.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
D.
reactor
Indicates a relationship where an entity functions as or is associated with a nuclear or chemical reactor system.
-
E.
usesEffectType
Indicates that an entity employs or is associated with a particular type or category of effect in its operation or behavior.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632b7fb88190821f213620719d6b |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.