Triple
T19187725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 American League Championship Series |
E469747
|
entity |
| Predicate | royalsLeagueSeed |
P18175
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [2015 American League Championship Series, royalsLeagueSeed, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalsLeagueSeed Context triple: [2015 American League Championship Series, royalsLeagueSeed, 1]
-
A.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
B.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
C.
runnerUpSeed
Indicates that one entity is the competitor or team assigned the second-best (runner-up) seed or ranking in a tournament or competition relative to another entity.
-
D.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
E.
topSeedWins
Indicates that in a competitive matchup, the highest-ranked (top-seeded) participant emerges as the winner.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f89f3ebc8190ba01ae075ffc77df |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.