Triple
T18585382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCoy Stadium |
E454223
|
entity |
| Predicate | longestGameDateStart |
P132670
|
FINISHED |
| Object | April 18, 1981 |
—
|
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: April 18, 1981 | Statement: [McCoy Stadium, longestGameDateStart, April 18, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestGameDateStart Context triple: [McCoy Stadium, longestGameDateStart, April 18, 1981]
-
A.
longestWinningStreakStart
Indicates the point in time or sequence at which an entity’s longest continuous winning streak begins.
-
B.
longestGameTeams
Indicates the teams that participated in the game with the longest duration within a given set of games or season.
-
C.
mostGoalsInSingleGameDate
Indicates the date on which an entity achieved its highest number of goals scored in a single game.
-
D.
typicalGameDate
Indicates the usual or standard calendar date on which a particular game is played or scheduled to occur.
-
E.
longestWinningStreakEnd
Indicates the point in time or event at which an entity’s longest continuous winning streak comes to an end.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b0dff08190a3be481faec34a3c |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:44 a.m.