Triple
T26765584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | hasQuarkModelClassification |
P133528
|
FINISHED |
| Object | decuplet baryon |
—
|
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: decuplet baryon | Statement: [Ξ*− (dss), hasQuarkModelClassification, decuplet baryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuarkModelClassification Context triple: [Ξ*− (dss), hasQuarkModelClassification, decuplet baryon]
-
A.
quarkModel
chosen
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).
-
B.
quarkModelPredictedBy
Indicates that a quark model is predicted, proposed, or derived by a particular theory, framework, or researcher.
-
C.
hasQuarkFlavors
Indicates that an entity (such as a particle) possesses specific types (flavors) of quarks as its constituents.
-
D.
hasQuark
Indicates that one entity possesses, contains, or is composed of the other entity as a quark.
-
E.
isModelOf
Indicates that one entity serves as a representation or abstraction that captures the structure or behavior of another 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 3:59 a.m.