Triple
T20538532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chievo Verona |
E504264
|
entity |
| Predicate | firstPromotionToSerieA |
P140462
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Chievo Verona, firstPromotionToSerieA, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPromotionToSerieA Context triple: [Chievo Verona, firstPromotionToSerieA, 2001]
-
A.
firstPromotionToPremierLeague
Indicates that this event marks an entity’s first-ever promotion to the Premier League.
-
B.
neverRelegatedFromSerieA
Indicates that a football club has never been relegated from Italy’s top division, Serie A, throughout its participation history.
-
C.
hasPromotionToTopDivisionFrom
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
-
D.
firstSeasonInTopFlight
Indicates the season in which an entity (typically a team or club) first competed in the highest level of a league or competition.
-
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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a29006008190aa1ee3224c75ff4b |
completed | April 20, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
| PDg | Predicate description generation | batch_69e5a6a824748190bbe6192d73f3c613 |
completed | April 20, 2026, 4:08 a.m. |
Created at: April 16, 2026, 11:37 a.m.