Triple
T12500100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 National League Championship Series |
E298797
|
entity |
| Predicate | losingTeamSeed |
P105311
|
FINISHED |
| Object | No. 1 seed in National League |
—
|
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: No. 1 seed in National League | Statement: [2007 National League Championship Series, losingTeamSeed, No. 1 seed in National League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: losingTeamSeed Context triple: [2007 National League Championship Series, losingTeamSeed, No. 1 seed in National League]
-
A.
losingTeamDivision
Indicates the league division to which the team that lost a given game or match belongs.
-
B.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
C.
losingTeamCity
Indicates the city associated with the team that lost a particular game or competition.
-
D.
losingTeamLeague
Indicates that a team is the losing side in a game or match within a particular league.
-
E.
losingTeamNickname
Indicates the nickname of the team that lost in a given game or competition.
- 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_69d6ada4cd388190ae3bbf83ff87057a |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e87e0e88190bc49dcfe4954c7e0 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:57 p.m.