Triple
T26765510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charm quark |
E674925
|
entity |
| Predicate | formsHadrons |
P23054
|
FINISHED |
| Object | charmed mesons |
—
|
NE NERFINISHED |
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: charmed mesons | Statement: [charm quark, formsHadrons, charmed mesons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsHadrons Context triple: [charm quark, formsHadrons, charmed mesons]
-
A.
hasBranchingRatioToHadrons
Indicates the fraction of a particle’s decays that result in hadronic final states (i.e., decays into hadrons).
-
B.
quarkModel
Indicates that one entity represents or employs a quark-based theoretical model to describe the internal structure or behavior of another entity (such as a particle or system).
-
C.
decayWidth
Indicates the total probability per unit time (or corresponding energy measure) that an unstable particle will decay via all possible channels.
-
D.
decayProduct
Indicates that one entity is the resulting product formed when another entity undergoes a decay process.
-
E.
hasValenceQuarks
chosen
Indicates that one entity possesses the specified quarks as its constituent valence quarks.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 3:59 a.m.