Triple
T9757146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRC Region I |
E236580
|
entity |
| Predicate | overseesFacilityType |
P11568
|
FINISHED |
| Object | nuclear power plant |
—
|
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: nuclear power plant | Statement: [NRC Region I, overseesFacilityType, nuclear power plant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overseesFacilityType Context triple: [NRC Region I, overseesFacilityType, nuclear power plant]
-
A.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
B.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
operatesFacility
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
D.
regulatesFacility
chosen
Indicates that one entity has authority to control, oversee, or set rules governing the operation or behavior of a facility.
-
E.
primaryFacilityType
Indicates the main or predominant type or category of facility associated with an entity.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda046a4048190a2c66321a9911817 |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.