Triple

T22813587
Position Surface form Disambiguated ID Type / Status
Subject Υ(4S) E565043 entity
Predicate isResonanceIn P149827 FINISHED
Object e^+ e^- → hadrons cross section near 10.58 GeV 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: e^+ e^- → hadrons cross section near 10.58 GeV | Statement: [Υ(4S), isResonanceIn, e^+ e^- → hadrons cross section near 10.58 GeV]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isResonanceIn
Context triple: [Υ(4S), isResonanceIn, e^+ e^- → hadrons cross section near 10.58 GeV]
  • A. isResonance
    Indicates that one entity vibrates or responds in harmony with another, typically amplifying or reinforcing its effect or signal.
  • B. isResonantBecause
    Indicates that one entity resonates or harmonizes with another specifically due to a stated cause or underlying reason.
  • C. isResonantObject
    Indicates that one entity functions as an object capable of resonating (physically or metaphorically) in response to another entity or influence.
  • 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. isNonResonant
    Indicates that the entity does not exhibit resonance or resonant behavior under the relevant conditions.
  • 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d61c6f081908d3911710b3aff51 completed April 29, 2026, 3:39 a.m.
PD Predicate disambiguation batch_69eed2cb30f481909566369f515f6eff completed April 27, 2026, 3:06 a.m.
PDg Predicate description generation batch_69eeeb5681f88190821129ced752f190 completed April 27, 2026, 4:51 a.m.
Created at: April 17, 2026, 3:32 p.m.