Triple
T2604233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL League One |
E58618
|
entity |
| Predicate | playOffParticipants |
P33368
|
FINISHED |
| Object | teams finishing 3rd to 6th |
—
|
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: teams finishing 3rd to 6th | Statement: [EFL League One, playOffParticipants, teams finishing 3rd to 6th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playOffParticipants Context triple: [EFL League One, playOffParticipants, teams finishing 3rd to 6th]
-
A.
playoffParticipation
chosen
Indicates that an entity takes part in a postseason playoff competition within a given league or tournament.
-
B.
finalTournamentParticipants
Indicates that the specified entities are the participants who qualified for and compete in the final round of a tournament.
-
C.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
D.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
-
E.
playoffSeed
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.