Triple
T36509062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bokke |
E899848
|
entity |
| Predicate | notableFlyHalf |
P204906
|
FINISHED |
| Object | Handré Pollard |
E277751
|
NE 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: Handré Pollard | Statement: [Bokke, notableFlyHalf, Handré Pollard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFlyHalf Context triple: [Bokke, notableFlyHalf, Handré Pollard]
-
A.
notableGoalScorer
Indicates that the subject is recognized for having scored a significant or noteworthy number of goals, typically in a sports context.
-
B.
Mitchell Pearce
Indicates a relationship or action involving the person named Mitchell Pearce, such as participation in an event, association with a team, or involvement in a specific role or activity.
-
C.
notableCornerback
Indicates that the subject is recognized as an especially distinguished or prominent cornerback in American football.
-
D.
notableForward
Indicates that an entity is prominently recognized or distinguished as a forward in a particular context, such as a sports team or competition.
-
E.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game of a competition.
- F. None of above. chosen
Provenance (5 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6d62f2c8190a2f2576cdadbd1bf |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:10 p.m.