Triple
T7821620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Faber |
E181141
|
entity |
| Predicate | bannedPitchGrandfathered |
P72781
|
FINISHED |
| Object | spitball |
—
|
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: spitball | Statement: [Red Faber, bannedPitchGrandfathered, spitball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedPitchGrandfathered Context triple: [Red Faber, bannedPitchGrandfathered, spitball]
-
A.
bannedAfter
Indicates that one entity becomes prohibited or forbidden only after the occurrence or establishment of another specified entity or event.
-
B.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
C.
lifetimeBanFromBaseball
Indicates that an individual has been permanently prohibited from participating in any official baseball activities or events.
-
D.
bannedInContextOf
chosen
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
E.
hasJetBan
Indicates that an entity is subject to a prohibition or restriction on the use or operation of jet aircraft.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa083fe88190a77efb7cfee4bd6f |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:41 p.m.