Triple
T26341368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Major League Baseball All-Star Game |
E662653
|
entity |
| Predicate | runSupportMVP |
P160424
|
FINISHED |
| Object | Mike Trout RBI triple |
—
|
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: Mike Trout RBI triple | Statement: [2014 Major League Baseball All-Star Game, runSupportMVP, Mike Trout RBI triple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runSupportMVP Context triple: [2014 Major League Baseball All-Star Game, runSupportMVP, Mike Trout RBI triple]
-
A.
runsVia
Indicates that a process, operation, or connection is executed, routed, or carried out through a specified intermediate channel, path, or mechanism.
-
B.
runTimeSupport
Indicates that one entity provides or requires support for another entity during its execution at run time.
-
C.
runBy
Indicates that an entity is operated, managed, or controlled by another entity.
-
D.
runnerOnFirst
Indicates that there is a baserunner currently occupying first base.
-
E.
runsWith
Indicates that one entity runs together alongside another entity, typically at the same time and place.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa2af708190a41199a1bd022ed2 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 10:39 p.m.