Triple
T13314615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UE Lleida |
E317157
|
entity |
| Predicate | relegationFromSegundaDivision |
P100906
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [UE Lleida, relegationFromSegundaDivision, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationFromSegundaDivision Context triple: [UE Lleida, relegationFromSegundaDivision, 1994]
-
A.
relegationFromSecondTierTo
chosen
Indicates that an entity is demoted from the second-highest competitive level or division to a specified lower tier or league.
-
B.
relegationToJ2
Indicates that a team or club is demoted from a higher football division to Japan’s J2 League.
-
C.
relegatedFromLigaMX
Indicates that a team has been demoted from competing in Liga MX to a lower division.
-
D.
relegatedFrom
Indicates that an entity has been demoted, downgraded, or moved from a higher status, level, or position to a lower one, typically as a result of performance or evaluation.
-
E.
relegationHistory
Indicates that one entity has a documented record of being moved to a lower status, tier, or division within a hierarchical system over time.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:29 p.m.