Triple
T5528566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFL |
E144987
|
entity |
| Predicate | hasRelegationPlacesFromChampionship |
P9667
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [EFL, hasRelegationPlacesFromChampionship, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelegationPlacesFromChampionship Context triple: [EFL, hasRelegationPlacesFromChampionship, 3]
-
A.
hasRelegationPlayOff
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
-
B.
hasRelegationTo
chosen
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
C.
hasPromotionRelegation
Indicates that there is a system in which entities can move up (promotion) or down (relegation) between hierarchical levels based on defined criteria or performance.
-
D.
divisionPlayedIn
Indicates that an entity (such as a team or player) participated in or was a member of a particular competitive division.
-
E.
associatedWithChampionshipTeams
Indicates a relationship where an entity has a connection or involvement with one or more championship-winning teams.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8b6c348190b7d414dc1907d09a |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.