Triple
T23899135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Six Nations Championship Grand Slam |
E600990
|
entity |
| Predicate | decidingMatchCity |
P25324
|
FINISHED |
| Object | Dublin |
—
|
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: Dublin | Statement: [2003 Six Nations Championship Grand Slam, decidingMatchCity, Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingMatchCity Context triple: [2003 Six Nations Championship Grand Slam, decidingMatchCity, Dublin]
-
A.
decidingGameCity
Indicates the city where the decisive or final game of a series, match, or competition takes place.
-
B.
decidingMatchFor
Indicates a relationship where one entity is chosen or determined as the appropriate or final match for another entity among possible alternatives.
-
C.
finalMatchCity
chosen
Indicates the city where the final match of a competition or tournament takes place.
-
D.
decisiveMatchOf
Indicates that one entity is a match for another in a way that determines or strongly influences a final outcome or decision.
-
E.
decisiveGameVenue
Indicates the location where the final, outcome-determining game of a series or competition is held.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddca9708190acd3e9edc9b5940b |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.