Triple
T15522018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-14 |
E368991
|
entity |
| Predicate | nuclearSpinParity |
P76189
|
FINISHED |
| Object | 1+ |
—
|
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: 1+ | Statement: [nitrogen-14, nuclearSpinParity, 1+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearSpinParity Context triple: [nitrogen-14, nuclearSpinParity, 1+]
-
A.
hasSpinParity
chosen
Indicates that a particle or system possesses a specific spin parity value characterizing its combined spin and intrinsic symmetry properties.
-
B.
hasSpinMultiplicity
Indicates that an entity is associated with a specific spin multiplicity value, representing the number of possible spin states in its quantum mechanical description.
-
C.
hasIntrinsicParity
Indicates that an entity possesses a specific intrinsic parity value characterizing its behavior under spatial inversion.
-
D.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
-
E.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
- 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_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_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:04 a.m.