Triple

T26099819
Position Surface form Disambiguated ID Type / Status
Subject England vs Australia E658365 entity
Predicate rivalryCharacterizedBy P159938 FINISHED
Object high public interest 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: high public interest | Statement: [England vs Australia, rivalryCharacterizedBy, high public interest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rivalryCharacterizedBy
Context triple: [England vs Australia, rivalryCharacterizedBy, high public interest]
  • A. rivalryCharacterizedBy chosen
    Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
  • B. rivalryCharacterization
    Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
  • C. involvesRivalryBetween
    Indicates a relationship in which two or more entities are engaged in rivalry or competitive opposition with one another.
  • D. rivalryBasis
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • E. typeOfRivalry
    Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
  • 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_69ee5bc09c288190bc42a11972841383 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f6073a39408190994ac1c8983a7c0b completed May 2, 2026, 2:16 p.m.
PD Predicate disambiguation batch_69f602d07590819085ac34b189613104 completed May 2, 2026, 1:57 p.m.
Created at: April 26, 2026, 7:54 p.m.