Triple
T32959804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Gas-cooled Reactor |
E843202
|
entity |
| Predicate | graphiteRole |
P41700
|
FINISHED |
| Object | neutron moderation |
—
|
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: neutron moderation | Statement: [Advanced Gas-cooled Reactor, graphiteRole, neutron moderation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphiteRole Context triple: [Advanced Gas-cooled Reactor, graphiteRole, neutron moderation]
-
A.
carbonRole
chosen
Indicates the functional role or involvement that an entity has in relation to carbon within a given process, system, or context.
-
B.
gammaRole
Indicates a tertiary or supporting role that an entity plays within a structured hierarchy of roles or participants in an event or relationship.
-
C.
roleInPrometheus
Indicates that an entity has a specific role or function within the Prometheus system or context.
-
D.
carbonateRole
Indicates a role or function that an entity has specifically in relation to carbonate (e.g., producing, modifying, transporting, or otherwise acting on carbonate).
-
E.
carbonStorageRole
Indicates the role or function an entity has in storing or sequestering carbon.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d17a0d88819082ad29b5ec8b2aec |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.