Triple
T15522101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-15 |
E368992
|
entity |
| Predicate | nuclearProperty |
P118995
|
FINISHED |
| Object | NMR-active nucleus |
—
|
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: NMR-active nucleus | Statement: [nitrogen-15, nuclearProperty, NMR-active nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearProperty Context triple: [nitrogen-15, nuclearProperty, NMR-active nucleus]
-
A.
hasNuclearPhase
Indicates that an entity undergoes or possesses a distinct stage or period characterized by nuclear-related processes, properties, or activities.
-
B.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
-
C.
nuclearMaterial
Indicates that the subject entity is or contains nuclear material, or is directly associated with nuclear substances used for energy, research, or weapons.
-
D.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
E.
nuclearPolicy
Indicates the stance, rules, or strategic approach an entity adopts regarding the development, possession, deployment, or use of nuclear weapons or nuclear technology.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0403543188190abac49d2b9decb89 |
completed | April 16, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57165288190979b7acb71ad5145 |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 4:04 a.m.