Triple
T6319941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1926 World Series |
E141711
|
entity |
| Predicate | babeRuthGame4HomeRuns |
P14862
|
FINISHED |
| Object | 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: 3 | Statement: [1926 World Series, babeRuthGame4HomeRuns, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: babeRuthGame4HomeRuns Context triple: [1926 World Series, babeRuthGame4HomeRuns, 3]
-
A.
homeRuns
chosen
Indicates the number of home runs a player hits, or that a specific home run event occurs, in a baseball context.
-
B.
babeRuthScorelessInningsStreakEndedInGame
Indicates that Babe Ruth’s streak of consecutive scoreless innings came to an end during the specified game.
-
C.
homeRunRecordSurpassedBy
Indicates that one entity’s home run record has been exceeded or broken by another entity.
-
D.
babeRuthRole
Indicates that one entity serves in the specific role or capacity associated with Babe Ruth (e.g., as a legendary baseball player or iconic sports figure) in relation to another entity.
-
E.
homeRunType
Indicates the specific kind of home run that was hit in a baseball play (e.g., solo, two-run, three-run, grand slam).
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c4ed7c8190bd066dc7cd3d1329 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.