Triple
T26759488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993–94 La Liga season |
E674759
|
entity |
| Predicate | relegationPlayOff |
P31084
|
FINISHED |
| Object | played |
—
|
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: played | Statement: [1993–94 La Liga season, relegationPlayOff, played]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationPlayOff Context triple: [1993–94 La Liga season, relegationPlayOff, played]
-
A.
relegationRound
Indicates that entities are involved in a stage or match of a competition where participants risk being demoted to a lower division or tier.
-
B.
relegationSystem
Indicates a system in which entities are moved to a lower tier or level based on their performance or ranking within a structured hierarchy.
-
C.
hasRelegationPlayOff
chosen
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
-
D.
relegationFromSecondTierTo
Indicates that an entity is demoted from the second-highest competitive level or division to a specified lower tier or league.
-
E.
relegationBasis
Indicates the criterion or grounds on which an entity is demoted, downgraded, or relegated from a higher to a lower status or level.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618dafb6c8190b4f53a7fcbf967e3 |
completed | May 2, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:57 a.m.