Triple
T30781018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babe Ruth’s alleged called shot in Game 3 |
E783811
|
entity |
| Predicate | hasGameNumber |
P102007
|
FINISHED |
| Object | Game 3 |
—
|
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: Game 3 | Statement: [Babe Ruth’s alleged called shot in Game 3, hasGameNumber, Game 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameNumber Context triple: [Babe Ruth’s alleged called shot in Game 3, hasGameNumber, Game 3]
-
A.
winningGameNumber
Indicates the specific game number in a series or sequence that results in a win for a given participant or side.
-
B.
associatedWithGameNumber
chosen
Indicates a relationship where something is linked or tied to a specific game identified by its number.
-
C.
gamePlayed
Indicates that a particular game is or was played by an entity (such as a person, team, or group) during a specific event or time.
-
D.
gameNumberInHistory
Indicates the position or sequence number of a particular game within a larger historical series or record of games.
-
E.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:41 p.m.