Triple
T15522044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-14 |
E368991
|
entity |
| Predicate | hasIsotopicPairWith |
P118991
|
FINISHED |
| Object | nitrogen-15 |
—
|
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: nitrogen-15 | Statement: [nitrogen-14, hasIsotopicPairWith, nitrogen-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsotopicPairWith Context triple: [nitrogen-14, hasIsotopicPairWith, nitrogen-15]
-
A.
commonIsotope
Indicates that two substances share the same most naturally abundant isotope of an element.
-
B.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
C.
hasIsospinMultiplet
Indicates that two or more particles belong to the same isospin multiplet, i.e., they are related by isospin symmetry and differ only in their isospin projection (such as charge states).
-
D.
hasTwinStructureWith
Indicates that two entities share an identical or nearly identical structural form, typically as corresponding or mirrored counterparts.
-
E.
isNucleusOfIsotope
Indicates that a given nucleus belongs to and characterizes a specific isotope.
- 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.