Triple
T34404651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 National League Championship Series |
E883077
|
entity |
| Predicate | higherSeedTeam |
P42750
|
FINISHED |
| Object | Atlanta Braves |
—
|
NE NERFINISHED |
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: Atlanta Braves | Statement: [1998 National League Championship Series, higherSeedTeam, Atlanta Braves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherSeedTeam Context triple: [1998 National League Championship Series, higherSeedTeam, Atlanta Braves]
-
A.
higherSeed
chosen
Indicates that one competitor or participant has been assigned a better (numerically lower) seed or ranking than another in a tournament or ordered competition.
-
B.
topTeam
Indicates that the referenced team is ranked as the best or leading team within a given group, competition, or context.
-
C.
scoringTeamSeed
Indicates the tournament seed or ranking assigned to the team that scored.
-
D.
topSeedWins
Indicates that in a competitive matchup, the highest-ranked (top-seeded) participant emerges as the winner.
-
E.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:59 a.m.