Triple
T1467841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDF |
E27064
|
entity |
| Predicate | mainGenerationTechnology |
P28887
|
FINISHED |
| Object | nuclear power |
—
|
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 | Statement: [EDF, mainGenerationTechnology, nuclear power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainGenerationTechnology Context triple: [EDF, mainGenerationTechnology, nuclear power]
-
A.
technologyGeneration
Indicates the generational level or era of technology associated with or used by an entity in relation to another.
-
B.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
C.
firstGenerationProduction
Indicates that the production or creation of something belongs to its initial or earliest generation in a sequence or lineage.
-
D.
technologyPioneered
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
E.
secondGenerationProduction
Indicates that the production activity involves a second generation of products, technologies, or processes derived from an earlier initial generation.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5d70a948190b50a6c1b36abc740 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8:01 p.m.