Triple

T7277790
Position Surface form Disambiguated ID Type / Status
Subject gluon E163072 entity
Predicate wasConfirmedBy P653 FINISHED
Object three-jet events in electron–positron collisions 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: three-jet events in electron–positron collisions | Statement: [gluon, wasConfirmedBy, three-jet events in electron–positron collisions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasConfirmedBy
Context triple: [gluon, wasConfirmedBy, three-jet events in electron–positron collisions]
  • A. confirmedBy chosen
    Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
  • B. confirmedFor
    Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
  • C. attestedBy
    Indicates that the existence, occurrence, or validity of something is supported, confirmed, or documented by a specified source or authority.
  • D. approvedBy
    Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
  • E. approvedAt
    Indicates the date and time at which an entity received formal approval.
  • 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_69c6885c5964819085b209701769877f completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eb8a0b4881908ff27c5a75bd4a95 completed March 27, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69c6e76a84a081908d4184c55b728e48 completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:59 p.m.