Triple
T32170308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 British & Irish Lions tour to South Africa |
E821691
|
entity |
| Predicate | opponentNickname |
P174978
|
FINISHED |
| Object | Springboks |
—
|
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: Springboks | Statement: [2021 British & Irish Lions tour to South Africa, opponentNickname, Springboks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentNickname Context triple: [2021 British & Irish Lions tour to South Africa, opponentNickname, Springboks]
-
A.
opponentTitle
Indicates that the object is the formal title or designation held by an opponent in a competitive or adversarial context.
-
B.
opponentFullName
Indicates the full name of an entity’s opponent in a competitive or adversarial context.
-
C.
rivalNickname
Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
-
D.
nicknameOfAntagonist
Indicates that one entity is a nickname or informal name used for an antagonist entity in a work or context.
-
E.
contrastsWithRivalNickname
Indicates that one nickname is intentionally different from and set in opposition to a rival nickname.
- F. None of above. chosen
Provenance (4 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 12:33 a.m.