Triple
T13708883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCD Mallorca |
E328715
|
entity |
| Predicate | promotionToLaLigaSeason |
P111275
|
FINISHED |
| Object | 2018–19 |
—
|
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: 2018–19 | Statement: [RCD Mallorca, promotionToLaLigaSeason, 2018–19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToLaLigaSeason Context triple: [RCD Mallorca, promotionToLaLigaSeason, 2018–19]
-
A.
promotionToSegundaDivision
Indicates that an entity achieves promotion or advancement to the Segunda División level in a competitive hierarchy.
-
B.
promotionToLigaMX
Indicates a relationship where a team or club achieves promotion to compete in the Liga MX league.
-
C.
promotionRelegation
Indicates a relationship where an entity’s status or level changes up or down within an ordered hierarchy based on performance or criteria.
-
D.
teamManagedToPromotion
Indicates that a team successfully achieved promotion to a higher level, league, or division.
-
E.
promotedFromPreviousSeason
Indicates that an entity has advanced or moved up from a lower level or division in the immediately preceding season.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad18d48c8190a26be865c31975d6 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.