Triple
T26765551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Σ*(1385) |
E674926
|
entity |
| Predicate | isResonanceOf |
P161215
|
FINISHED |
| Object | Σ baryon |
—
|
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: Σ baryon | Statement: [Σ*(1385), isResonanceOf, Σ baryon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResonanceOf Context triple: [Σ*(1385), isResonanceOf, Σ baryon]
-
A.
isResonance
Indicates that one entity vibrates or responds in harmony with another, typically amplifying or reinforcing its effect or signal.
-
B.
isResonanceIn
Indicates that something functions as or exhibits a resonance within a specified medium, system, or context.
-
C.
isResonantBecause
Indicates that one entity resonates or harmonizes with another specifically due to a stated cause or underlying reason.
-
D.
resonanceWith
Indicates a relationship where one entity aligns, harmonizes, or meaningfully connects with another in a way that amplifies or reinforces its effect or significance.
-
E.
isResonantObject
Indicates that one entity functions as an object capable of resonating (physically or metaphorically) in response to another entity or influence.
- 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_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. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:59 a.m.