Triple
T33431603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan vs South Africa (2015 Rugby World Cup) |
E856144
|
entity |
| Predicate | decisiveTryMinute |
P41440
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [Japan vs South Africa (2015 Rugby World Cup), decisiveTryMinute, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveTryMinute Context triple: [Japan vs South Africa (2015 Rugby World Cup), decisiveTryMinute, 80]
-
A.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
B.
decisiveTryScorer
Indicates that an entity scored a try that decisively determined the outcome of a match or competition.
-
C.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
D.
decisiveSection
Indicates that a particular section or segment is crucial in determining the overall outcome or result of something.
-
E.
decidingScoreTime
chosen
Indicates the point in time at which a decisive or game-determining score occurs.
- 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_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:36 a.m.