Triple
T6836953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serie B |
E157473
|
entity |
| Predicate | hasRelegationSpots |
P73443
|
FINISHED |
| Object | direct relegation places |
—
|
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: direct relegation places | Statement: [Serie B, hasRelegationSpots, direct relegation places]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelegationSpots Context triple: [Serie B, hasRelegationSpots, direct relegation places]
-
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
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.
hasRelegationPlacesFromLeagueOne
Indicates that there are designated relegation spots in League One from which teams are demoted to a lower division.
-
E.
hasRelegationHistory
Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d67c1c508190ab39b8aaaaacc628 |
completed | March 27, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:19 p.m.