Triple
T15767781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine Tar Incident |
E382268
|
entity |
| Predicate | scoreAtResumption |
P49538
|
FINISHED |
| Object | Royals leading 5–4 |
—
|
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: Royals leading 5–4 | Statement: [Pine Tar Incident, scoreAtResumption, Royals leading 5–4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoreAtResumption Context triple: [Pine Tar Incident, scoreAtResumption, Royals leading 5–4]
-
A.
scoreBeforePlay
Indicates that a particular score or point total existed prior to a specific play or action occurring.
-
B.
scoreAfterPlay
chosen
Indicates the numerical score that results immediately after a specific play or action has been completed.
-
C.
scoresWhen
Indicates that one entity achieves a score or points at the time or under the condition specified by another entity or event.
-
D.
seasonResumptionLocation
Indicates the location where a season (such as a sports league or series) is resumed after a break or interruption.
-
E.
seasonResumptionState
Indicates the current status or phase of a season’s restart or continuation after a pause or interruption.
- 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_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. |
Created at: April 10, 2026, 4:47 a.m.