Triple
T24734630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Major League Baseball season |
E618376
|
entity |
| Predicate | tonyGwynnChaseFor |
P96361
|
FINISHED |
| Object | .400 batting average |
—
|
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: .400 batting average | Statement: [1994 Major League Baseball season, tonyGwynnChaseFor, .400 batting average]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tonyGwynnChaseFor Context triple: [1994 Major League Baseball season, tonyGwynnChaseFor, .400 batting average]
-
A.
battingMilestone
chosen
Indicates reaching a significant achievement or benchmark related to batting performance, such as a notable run total or record.
-
B.
homeRunRecordSurpassedBy
Indicates that one entity’s home run record has been exceeded or broken by another entity.
-
C.
reached600HomeRuns
Indicates that an entity has achieved a career total of at least 600 home runs.
-
D.
winningHomeRunHitter
Indicates the player who hit the home run that ultimately decided the victory for their team in a game.
-
E.
Ryne SandbergRunsScored
Indicates that Ryne Sandberg scored one or more runs in the referenced game or play.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:03 a.m.