Triple
T24867997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Rugby League World Cup |
E622339
|
entity |
| Predicate | alsoUsedVenuesIn |
P68646
|
FINISHED |
| Object | Wales |
—
|
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: Wales | Statement: [2021 Rugby League World Cup, alsoUsedVenuesIn, Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoUsedVenuesIn Context triple: [2021 Rugby League World Cup, alsoUsedVenuesIn, Wales]
-
A.
usedVenuesFrom
Indicates that one entity has made use of or operated in venues associated with another entity.
-
B.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
C.
usesMultipleVenuesIn
chosen
Indicates that an entity conducts its activities or events across more than one venue within a specified location or context.
-
D.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
E.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:23 a.m.