Triple
T12764266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OHL playoffs |
E305077
|
entity |
| Predicate | topSeedPlays |
P18175
|
FINISHED |
| Object | eighth seed in first round |
—
|
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: eighth seed in first round | Statement: [OHL playoffs, topSeedPlays, eighth seed in first round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topSeedPlays Context triple: [OHL playoffs, topSeedPlays, eighth seed in first round]
-
A.
topSeedByeToSemifinals
Indicates that the top-seeded participant automatically advances directly to the semifinals without playing earlier rounds.
-
B.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
C.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
D.
seedOfWinner
Indicates that one entity is the seed or ranking position assigned to the entity that wins a competition or match.
-
E.
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.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8f9f588190bffdea878856204b |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.