Triple
T15767766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pine Tar Incident |
E382268
|
entity |
| Predicate | batIssue |
P120257
|
FINISHED |
| Object | excessive pine tar on George Brett's bat |
—
|
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: excessive pine tar on George Brett's bat | Statement: [Pine Tar Incident, batIssue, excessive pine tar on George Brett's bat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: batIssue Context triple: [Pine Tar Incident, batIssue, excessive pine tar on George Brett's bat]
-
A.
bats
Indicates that one entity hits or strikes another entity, typically using a bat or similar implement.
-
B.
batFlip
Indicates the action of a batter flipping or tossing their bat, typically in a celebratory or expressive manner after a hit.
-
C.
batsUsed
Indicates that one or more bats are employed or utilized in relation to a particular entity or event.
-
D.
backdoorPilotIn
Indicates that one work (typically an episode) is used to introduce and test characters or concepts intended for a potential new series set within the same universe.
-
E.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
- 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.