Triple
T26765552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Σ*(1385) |
E674926
|
entity |
| Predicate | isExcitationOf |
P149824
|
FINISHED |
| Object | ground-state Σ 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: ground-state Σ baryon | Statement: [Σ*(1385), isExcitationOf, ground-state Σ baryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExcitationOf Context triple: [Σ*(1385), isExcitationOf, ground-state Σ baryon]
-
A.
excites
Indicates that one entity causes another entity to become excited, stimulated, or activated, typically by increasing its energy or arousal level.
-
B.
isRadialExcitationOf
chosen
Indicates that one state or mode is a higher radial excitation (same quantum numbers except for radial quantum number) of another state or mode.
-
C.
isAReactionTo
Indicates that one event, action, or state occurs as a direct response or consequence of another.
-
D.
dominantExcitationSource
Indicates that one entity serves as the primary or most influential source of excitation affecting another entity or system.
-
E.
actuatedBy
Indicates that an action, process, or mechanism is initiated, driven, or controlled by a specific agent or cause.
- 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_69f6192758648190ba2c0bfc9904994e |
completed | May 2, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:59 a.m.