Triple
T189473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | deuteron |
E3686
|
entity |
| Predicate | hasBaryonNumber |
P5747
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [deuteron, hasBaryonNumber, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaryonNumber Context triple: [deuteron, hasBaryonNumber, 2]
-
A.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
B.
hasBranchingRatioToLeptons
Indicates the proportion of a particle’s decays that result in leptons among all its possible decay channels.
-
C.
isGaugeBosonOf
Indicates that one particle serves as the gauge boson mediating the fundamental interaction associated with another entity (such as a force or symmetry group).
-
D.
hasChargeConjugation
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
E.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2594c385481909e1e088e45c460a4 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25672332081909386f35f3ca15dd2 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a25738b5108190866fd704fceee18a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.