Triple
T5603184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby World Cup 2003 matches |
E147168
|
entity |
| Predicate | timeOfDecidingScore |
P41440
|
FINISHED |
| Object | extra time |
—
|
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: extra time | Statement: [Rugby World Cup 2003 matches, timeOfDecidingScore, extra time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDecidingScore Context triple: [Rugby World Cup 2003 matches, timeOfDecidingScore, extra time]
-
A.
decidingScoreTime
chosen
Indicates the point in time at which a decisive or game-determining score occurs.
-
B.
decisiveScoreType
Indicates the type or category of score used to determine a decisive outcome in a comparison or decision process.
-
C.
decidingScoreTeam
Indicates the team whose score ultimately determines the outcome or winner in a game or match.
-
D.
decidingScoreDistance
Indicates the point or score difference by which a contest, game, or decision is ultimately determined.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
- 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_69c009043d648190a7af89698ccf1e3e |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020dce10c8190bf456602eec211d4 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.