Triple
T33515777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Danube |
E858360
|
entity |
| Predicate | nuclearConfiguration |
P118995
|
FINISHED |
| Object | plutonium core fission device |
—
|
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: plutonium core fission device | Statement: [Blue Danube, nuclearConfiguration, plutonium core fission device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearConfiguration Context triple: [Blue Danube, nuclearConfiguration, plutonium core fission device]
-
A.
nuclearProperty
chosen
Indicates a relationship where an entity possesses or is characterized by a specific nuclear-related attribute, such as structure, behavior, or interaction at the atomic nucleus level.
-
B.
nuclearOrganization
Indicates the relationship in which an entity organizes, arranges, or structures components within the cell nucleus.
-
C.
nucleusType
Indicates the specific kind or classification of nucleus associated with an entity.
-
D.
nuclearSpin
Indicates that an entity possesses a specific nuclear spin value or nuclear spin state.
-
E.
nuclearIsomericStates
Indicates that one nuclear species exists in different isomeric (metastable) energy states distinguished by their nuclear energy configuration.
- 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_69f3497721848190978fbee5e0a526f8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:39 a.m.