Triple
T15767778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine Tar Incident |
E382268
|
entity |
| Predicate | gameResumptionDate |
P120258
|
FINISHED |
| Object | 1983-08-18 |
—
|
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: 1983-08-18 | Statement: [Pine Tar Incident, gameResumptionDate, 1983-08-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameResumptionDate Context triple: [Pine Tar Incident, gameResumptionDate, 1983-08-18]
-
A.
seasonResumptionDate
Indicates the date on which a previously paused or off-season period resumes or restarts.
-
B.
rematchDate
Indicates the date on which a subsequent or repeat contest between the same parties is scheduled or took place.
-
C.
game3Date
Indicates the calendar date on which the third game in a series or sequence takes place.
-
D.
rescheduledTo
Indicates that an event or action has been moved from its original time to a new specified time.
-
E.
revivalEndTime
Indicates the point in time at which a revival process, event, or restored state 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051951bac8190a7d45f3612c6de72 |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.