Triple
T15521979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nitrogen-13 |
E368990
|
entity |
| Predicate | bindingEnergyPerNucleon |
P7805
|
FINISHED |
| Object | about 7.5 MeV |
—
|
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: about 7.5 MeV | Statement: [nitrogen-13, bindingEnergyPerNucleon, about 7.5 MeV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingEnergyPerNucleon Context triple: [nitrogen-13, bindingEnergyPerNucleon, about 7.5 MeV]
-
A.
hasBindingEnergy
chosen
Indicates that one entity possesses or is characterized by a specific amount of binding energy associated with its formation or stability.
-
B.
maximumCenterOfMassEnergyPerNucleonPair
Indicates the highest achievable center-of-mass energy available per pair of nucleons participating in a collision or interaction.
-
C.
thermalNeutronCaptureCrossSection
Indicates the probability that a nucleus will capture a thermal (low-energy) neutron, expressed as an effective interaction cross-sectional area.
-
D.
beamEnergy
Indicates the amount of energy carried by or assigned to a beam in a physical or engineered system.
-
E.
hasNeutronNumber
Indicates that an entity (typically an atom or nuclide) has a specified number of neutrons in its nucleus.
- 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.