Triple
T33660389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R91 Charles de Gaulle |
E862334
|
entity |
| Predicate | navalReactorType |
P171553
|
FINISHED |
| Object | K15 nuclear reactor |
—
|
NE NERFINISHED |
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: K15 nuclear reactor | Statement: [R91 Charles de Gaulle, navalReactorType, K15 nuclear reactor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalReactorType Context triple: [R91 Charles de Gaulle, navalReactorType, K15 nuclear reactor]
-
A.
propulsionReactorType
chosen
Indicates the type or kind of reactor used as the primary source of propulsion.
-
B.
hasNuclearReactorType
Indicates that an entity possesses or is equipped with a specific type or classification of nuclear reactor.
-
C.
navalStandardType
Indicates the specific naval standard or classification system under which an entity (such as a vessel, equipment, or procedure) is defined or regulated.
-
D.
naveConstruction
Indicates the construction or building activity specifically related to a church’s nave.
-
E.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa36f640819098051eff7e5a5787 |
completed | May 3, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.