Triple
T7600624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | baryon decuplet |
E179972
|
entity |
| Predicate | hasIsospinMultiplet |
P78108
|
FINISHED |
| Object | Δ(1232) |
—
|
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: Δ(1232) | Statement: [baryon decuplet, hasIsospinMultiplet, Δ(1232)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsospinMultiplet Context triple: [baryon decuplet, hasIsospinMultiplet, Δ(1232)]
-
A.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
B.
hasIsospinThirdComponent
Indicates that an entity is associated with a specific value of the third (z) component of its isospin in isospin space.
-
C.
hasWeakIsospin
Indicates that an entity possesses a specified value of weak isospin, representing its charge under the weak nuclear interaction.
-
D.
isMassEigenstateOf
Indicates that one entity is a quantum state with a definite mass that results from diagonalizing the mass operator (or mass matrix) associated with the other entity.
-
E.
hasMultiple
Indicates that an entity is associated with more than one instance or occurrence of another related entity.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d9c55c8190841f3bf3225c096a |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.