Triple
T21531762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England–Wales football rivalry |
E531246
|
entity |
| Predicate | notableMatchDate |
P69773
|
FINISHED |
| Object | 2016-06-16 |
—
|
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: 2016-06-16 | Statement: [England–Wales football rivalry, notableMatchDate, 2016-06-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMatchDate Context triple: [England–Wales football rivalry, notableMatchDate, 2016-06-16]
-
A.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
B.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
C.
dateOfNotableGame
chosen
Indicates the calendar date on which a particular notable game took place.
-
D.
notableMatchVenueFor
Indicates that a venue is notably associated with hosting a particular match or game.
-
E.
firstMLSMatchDate
Indicates the calendar date on which an entity (typically a player or team) participated in its first official Major League Soccer (MLS) match.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0a0e7c8190bbb7ed5c4dfe33af |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.