Triple

T32092541
Position Surface form Disambiguated ID Type / Status
Subject Pool D (2007 Rugby World Cup) E819633 entity
Predicate hasPoolOpponent P116426 FINISHED
Object Pool A (2007 Rugby World Cup) 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: Pool A (2007 Rugby World Cup) | Statement: [Pool D (2007 Rugby World Cup), hasPoolOpponent, Pool A (2007 Rugby World Cup)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPoolOpponent
Context triple: [Pool D (2007 Rugby World Cup), hasPoolOpponent, Pool A (2007 Rugby World Cup)]
  • A. wasOpponentOf
    Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
  • B. associatedOpponent chosen
    Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
  • C. hasOpposingSide
    Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
  • D. hasOpposingTeamsLedBy
    Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
  • E. laterOpponent
    Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
  • 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_69f349004b2481908ce2e50af0d579a8 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fe87b609888190913b0c3f787ecdba completed May 9, 2026, 1:02 a.m.
PD Predicate disambiguation batch_69fe8731af48819092084f6f74bf052d completed May 9, 2026, 1 a.m.
Created at: May 1, 2026, 12:25 a.m.