Triple
T469987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 4 of the 2004 American League Championship Series |
E8533
|
entity |
| Predicate | walkOffType |
P15118
|
FINISHED |
| Object | 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: home run | Statement: [Game 4 of the 2004 American League Championship Series, walkOffType, home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkOffType Context triple: [Game 4 of the 2004 American League Championship Series, walkOffType, home run]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
-
C.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
-
D.
withdrewFrom
Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
-
E.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efef8b788190857ebf66df562d59 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.