Triple

T26762195
Position Surface form Disambiguated ID Type / Status
Subject Oxford University Archery Club E674833 entity
Predicate hasOpponentInVarsityMatch P86168 FINISHED
Object University of Cambridge 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: University of Cambridge | Statement: [Oxford University Archery Club, hasOpponentInVarsityMatch, University of Cambridge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOpponentInVarsityMatch
Context triple: [Oxford University Archery Club, hasOpponentInVarsityMatch, University of Cambridge]
  • A. wasOpponentOf chosen
    Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
  • B. hadPlayoffMatch
    Indicates that two competitors or teams participated in a playoff match against each other.
  • C. hasChampionshipMatch
    Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
  • D. conferencePlayedInCollege
    Indicates that a person participated in collegiate athletics within a specific athletic conference.
  • E. hasRivalStand
    Indicates that one entity maintains a competing or opposing stand, position, or operation in relation to another entity.
  • 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_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 27, 2026, 3:58 a.m.