Triple
T99358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Reorganization Act of 1974 |
E2005
|
entity |
| Predicate | separatedFunction |
P2195
|
FINISHED |
| Object | nuclear regulatory functions |
—
|
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 regulatory functions | Statement: [Energy Reorganization Act of 1974, separatedFunction, nuclear regulatory functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFunction Context triple: [Energy Reorganization Act of 1974, separatedFunction, nuclear regulatory functions]
-
A.
separatedFunctionFrom
chosen
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.