Triple
T4799016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boleyn Ground |
E106786
|
entity |
| Predicate | finalLeagueMatchDate |
P14672
|
FINISHED |
| Object | 2016-05-10 |
—
|
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-05-10 | Statement: [Boleyn Ground, finalLeagueMatchDate, 2016-05-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLeagueMatchDate Context triple: [Boleyn Ground, finalLeagueMatchDate, 2016-05-10]
-
A.
finalMatchDate
chosen
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
B.
finalMlbGameDate
Indicates the calendar date on which an entity’s final Major League Baseball game took place.
-
C.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
D.
semifinalDate
Indicates the scheduled calendar date on which a semifinal round of a competition or tournament takes place.
-
E.
finalGameLeague
Indicates that a game is the concluding or championship match within a particular league or league season.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.