Triple
T4189720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Thomson's "Shot Heard 'Round the World" |
E89002
|
entity |
| Predicate | baseRunners |
P54558
|
FINISHED |
| Object | Alvin Dark on third base |
—
|
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: Alvin Dark on third base | Statement: [Bobby Thomson's "Shot Heard 'Round the World", baseRunners, Alvin Dark on third base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseRunners Context triple: [Bobby Thomson's "Shot Heard 'Round the World", baseRunners, Alvin Dark on third base]
-
A.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
B.
runsByDefault
Indicates that an action, process, or behavior is executed automatically without requiring explicit configuration or invocation.
-
C.
runsBeneath
Indicates that one entity extends or moves below another entity along its length or span.
-
D.
runnerUpManager
Indicates that one entity serves as the manager or coach of another entity who finished as the runner-up in a competition or ranking.
-
E.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af04af4e44819098a9d7f91e65adf2 |
completed | March 9, 2026, 5:34 p.m. |
Created at: March 9, 2026, 3:46 p.m.