Triple
T11461329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacques Nienaber |
E271665
|
entity |
| Predicate | ledTeamAchievement |
P5917
|
FINISHED |
| Object | 2023 Rugby World Cup champions |
—
|
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: 2023 Rugby World Cup champions | Statement: [Jacques Nienaber, ledTeamAchievement, 2023 Rugby World Cup champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledTeamAchievement Context triple: [Jacques Nienaber, ledTeamAchievement, 2023 Rugby World Cup champions]
-
A.
teamAchievement
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
-
B.
hostedTeamAchievement
Indicates that an entity organized or hosted an event or context in which a team achieved a particular accomplishment.
-
C.
ledTeamIn
Indicates that one entity had primary leadership responsibility over a team in which the other entity participated or was involved.
-
D.
ledTeamTo
chosen
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
-
E.
teamHonor
Indicates that an honor, award, or recognition is attributed to or received by a team.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f384f08190b1150ed1389dd31a |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.