Triple
T36350591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam 2009 |
E895190
|
entity |
| Predicate | decidingMatchOpponent |
P166599
|
FINISHED |
| Object | Wales national rugby union team |
—
|
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: Wales national rugby union team | Statement: [Grand Slam 2009, decidingMatchOpponent, Wales national rugby union team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingMatchOpponent Context triple: [Grand Slam 2009, decidingMatchOpponent, Wales national rugby union team]
-
A.
decidingOpponent
Indicates that one entity is the opponent or counterpart responsible for making a decision that affects another entity.
-
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.
laterOpponent
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
D.
finalLeagueMatchOpponent
chosen
Indicates the opposing team or player faced in an entity’s final league match.
-
E.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.