Triple
T36350596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam 2009 |
E895190
|
entity |
| Predicate | decidingMatchScore |
P186011
|
FINISHED |
| Object | Wales 15–17 Ireland |
—
|
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: Wales 15–17 Ireland | Statement: [Grand Slam 2009, decidingMatchScore, Wales 15–17 Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingMatchScore Context triple: [Grand Slam 2009, decidingMatchScore, Wales 15–17 Ireland]
-
A.
decidingMatchScoreMargin
Indicates the point or score difference by which a deciding match is won or lost.
-
B.
decisiveGroupMatchScore
Indicates the degree to which a particular group match is clear, conclusive, or strongly favored over alternatives.
-
C.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
D.
decisiveScoreType
Indicates the type or category of score used to determine a decisive outcome in a comparison or decision process.
-
E.
decidingScoreTeam
Indicates the team whose score ultimately determines the outcome or winner in a game or match.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:09 p.m.