Triple
T34404680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 National League Championship Series |
E883077
|
entity |
| Predicate | notableHitterForBraves |
P7087
|
FINISHED |
| Object | Chipper Jones |
E77203
|
NE 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: Chipper Jones | Statement: [1998 National League Championship Series, notableHitterForBraves, Chipper Jones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHitterForBraves Context triple: [1998 National League Championship Series, notableHitterForBraves, Chipper Jones]
-
A.
notableBatter
chosen
Indicates that the subject is a batter who is particularly prominent, distinguished, or noteworthy in the context of batting.
-
B.
homeRunsNotedFor
Indicates that an entity is recognized or recorded specifically for its home runs.
-
C.
notablePitcher
Indicates that the subject is recognized as a distinguished or prominent pitcher in the context of baseball.
-
D.
winningHomeRunHitter
Indicates the player who hit the home run that ultimately decided the victory for their team in a game.
-
E.
notableShortstop
Indicates that the subject is recognized as a distinguished or prominent shortstop in baseball.
- F. None of above.
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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a370dcdd88c8190a16d10be2c6d16cc |
completed | June 20, 2026, 10:01 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.