Triple
T33431615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan vs South Africa (2015 Rugby World Cup) |
E856144
|
entity |
| Predicate | SouthAfricaPenaltyGoals |
P58329
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Japan vs South Africa (2015 Rugby World Cup), SouthAfricaPenaltyGoals, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SouthAfricaPenaltyGoals Context triple: [Japan vs South Africa (2015 Rugby World Cup), SouthAfricaPenaltyGoals, 2]
-
A.
SouthAfricaScore
Indicates the score or points achieved by South Africa in a particular event, match, or evaluation.
-
B.
penaltyScoredBy
Indicates that a penalty (typically in a game or sport) was successfully converted or scored by a particular participant.
-
C.
penaltyGoalPoints
chosen
Indicates that points are awarded for a goal scored from a penalty situation.
-
D.
penaltyShootoutScore
Indicates the number of goals each side scored during a penalty shootout used to decide a tied match.
-
E.
SouthAfricaTries
Indicates an attempt or effort made by South Africa to perform, achieve, or bring about a particular action or outcome.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:36 a.m.