Triple
T15521968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-13 |
E368990
|
entity |
| Predicate | nucleonNumber |
P5748
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [nitrogen-13, nucleonNumber, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nucleonNumber Context triple: [nitrogen-13, nucleonNumber, 13]
-
A.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
-
B.
hasMassNumber
chosen
Indicates that an atomic nucleus or isotope is associated with a specific mass number, representing the total count of protons and neutrons it contains.
-
C.
hasProtonNumber
Indicates that an entity (typically a chemical element or atom) possesses a specific number of protons in its nucleus.
-
D.
neutronNumberMostStableIsotope
Indicates the relationship that specifies the number of neutrons in the most stable (lowest-energy or longest-lived) isotope of an element.
-
E.
hasAtomicNumber
Indicates that one entity is the chemical element whose atomic number (number of protons in its nucleus) is given by the other entity.
- 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.