Triple
T23900218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vizela |
E601020
|
entity |
| Predicate | promotionToPrimeiraLiga |
P154003
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Vizela, promotionToPrimeiraLiga, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotionToPrimeiraLiga Context triple: [Vizela, promotionToPrimeiraLiga, 2021]
-
A.
promotionToPrimeraDivision
Indicates that an entity (typically a sports team) has achieved promotion to the Primera Division, moving up from a lower league or division.
-
B.
promotionToLaLigaSeason
Indicates that a team achieves promotion to participate in a specified La Liga season.
-
C.
promotionToSegundaDivision
Indicates that an entity achieves promotion or advancement to the Segunda División level in a competitive hierarchy.
-
D.
promotionToLigaMX
Indicates a relationship where a team or club achieves promotion to compete in the Liga MX league.
-
E.
managedPromotionToPremierLeagueWith
Indicates that one entity was responsible for managing or leading another entity to achieve promotion to the Premier League together.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:26 p.m.