Triple
T37566958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springbok Sevens |
E933981
|
entity |
| Predicate | rugbyWorldCupSevensHostNation |
P36997
|
FINISHED |
| Object | South Africa 2022 |
—
|
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: South Africa 2022 | Statement: [Springbok Sevens, rugbyWorldCupSevensHostNation, South Africa 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rugbyWorldCupSevensHostNation Context triple: [Springbok Sevens, rugbyWorldCupSevensHostNation, South Africa 2022]
-
A.
RugbyWorldCupHosts
chosen
Indicates that the specified country (or countries) served as the official host nation(s) for a particular edition of the Rugby World Cup.
-
B.
worldCupHost
Indicates that one entity serves as the host country or location for a particular FIFA World Cup tournament.
-
C.
rugbyWorldCupWinner
Indicates the team that won a given edition of the Rugby World Cup.
-
D.
rugbyWorldCupAppearance
Indicates that an entity has participated in at least one edition of the Rugby World Cup.
-
E.
worldCupSevens2018Opponent
Indicates that one entity was the opposing team faced by the other entity in a match during the 2018 Rugby World Cup Sevens.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.