Triple
T7600559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega minus baryon |
E179970
|
entity |
| Predicate | isResonance |
P78107
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Omega minus baryon, isResonance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResonance Context triple: [Omega minus baryon, isResonance, yes]
-
A.
isResonantObject
Indicates that one entity functions as an object capable of resonating (physically or metaphorically) in response to another entity or influence.
-
B.
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.
-
C.
usesHarmonics
Indicates that one entity employs harmonic frequencies or overtones of another entity or signal as part of its operation or behavior.
-
D.
isTunedTo
Indicates that one entity has been adjusted or configured to operate at, receive, or correspond to the frequency, channel, or setting of another entity.
-
E.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
- 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.