Triple
T33431602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan vs South Africa (2015 Rugby World Cup) |
E856144
|
entity |
| Predicate | decisiveTryScorer |
P179081
|
FINISHED |
| Object | Karne Hesketh |
—
|
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: Karne Hesketh | Statement: [Japan vs South Africa (2015 Rugby World Cup), decisiveTryScorer, Karne Hesketh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveTryScorer Context triple: [Japan vs South Africa (2015 Rugby World Cup), decisiveTryScorer, Karne Hesketh]
-
A.
decisivePenaltyScorer
Indicates that an entity scores a crucial penalty that decisively determines the outcome of a match or competition.
-
B.
decisiveScoreType
Indicates the type or category of score used to determine a decisive outcome in a comparison or decision process.
-
C.
decisiveGoalGame
Indicates that a game contains a goal or scoring event that definitively determines the winner or final outcome.
-
D.
deciderInKnockout
Indicates that an entity serves as the deciding factor or tiebreaker in determining the outcome of a knockout-stage contest or match.
-
E.
decidingScoreTime
Indicates the point in time at which a decisive or game-determining score occurs.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:36 a.m.