Triple

T24580472
Position Surface form Disambiguated ID Type / Status
Subject Stade Gilbert Brutus E608232 entity
Predicate hasEventHosted P50694 FINISHED
Object Rugby League World Cup matches 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: Rugby League World Cup matches | Statement: [Stade Gilbert Brutus, hasEventHosted, Rugby League World Cup matches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEventHosted
Context triple: [Stade Gilbert Brutus, hasEventHosted, Rugby League World Cup matches]
  • A. hasHostedVenue chosen
    Indicates that a particular venue has served as the location for hosting a specific event or activity.
  • B. hostedDuring
    Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
  • C. hasHostedSport
    Indicates that a place or organization has served as the venue or organizer for one or more sporting events.
  • D. hasBeenHostedIn
    Indicates that an event, show, or activity took place or was conducted at a particular location or venue in the past.
  • E. alsoHostsEventsIn
    Indicates that an entity, in addition to its primary location or context, serves as a venue or place where events are held in another specified location.
  • 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_69e2c4ce89248190ad99e18f0638dfbb completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a97fde9c81909d8de91b6358a015 completed April 30, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f2a6c1f07081908edf0b521767e79b completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:29 a.m.