Triple
T31573019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Series with Boston Red Sox |
E805615
|
entity |
| Predicate | notablePlayerExample |
P207459
|
FINISHED |
| Object | Mookie Betts |
E45616
|
NE 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: Mookie Betts | Statement: [World Series with Boston Red Sox, notablePlayerExample, Mookie Betts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerExample Context triple: [World Series with Boston Red Sox, notablePlayerExample, Mookie Betts]
-
A.
notableAthlete
Indicates that the subject is a well-known or distinguished athlete associated with the object (such as a sport, team, or organization).
-
B.
hasNotablePlayer
Indicates that an entity (such as a team or club) is associated with a player who is particularly distinguished, famous, or significant in its context.
-
C.
notableAthleteFrom
Indicates that an athlete is notably associated with or originates from a particular place or region.
-
D.
organNotablePlayer
Indicates that a person is a notable or distinguished player of a particular organ.
-
E.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game of a competition.
- F. None of above. chosen
Provenance (5 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d9d01dc8190b06a7c60a5a4b949 |
completed | June 11, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:20 p.m.