Triple
T3214660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 6 (1993 World Series) |
E67360
|
entity |
| Predicate | homeRunType |
P46257
|
FINISHED |
| Object | three-run home run |
—
|
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: three-run home run | Statement: [Game 6 (1993 World Series), homeRunType, three-run home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRunType Context triple: [Game 6 (1993 World Series), homeRunType, three-run home run]
-
A.
homeRuns
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
clinchingHomeRunType
Indicates the specific type or category of a home run that clinches or decisively secures a game, series, or title.
-
C.
homeRunRate
Indicates the frequency at which a player or team hits home runs relative to a specified number of opportunities (such as at-bats, plate appearances, or games).
-
D.
homeRunInteraction
Indicates an interaction where a batter successfully hits a home run, establishing the event and its participants.
-
E.
homeRunTitle
Indicates that one entity is the title or name given to a home run event associated with another entity.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab085a408190af9fb40acca31a5f |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.