Triple
T25330182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benevento Calcio |
E635127
|
entity |
| Predicate | firstPromotionToSerieB |
P184569
|
FINISHED |
| Object | 2015–16 |
—
|
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: 2015–16 | Statement: [Benevento Calcio, firstPromotionToSerieB, 2015–16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPromotionToSerieB Context triple: [Benevento Calcio, firstPromotionToSerieB, 2015–16]
-
A.
firstPromotionToSerieA
Indicates the event in which a team is promoted to Serie A for the first time in its history.
-
B.
promotionToPrimeraDivision
Indicates that an entity (typically a sports team) has achieved promotion to the Primera Division, moving up from a lower league or division.
-
C.
promotionToSegundaDivision
Indicates that an entity achieves promotion or advancement to the Segunda División level in a competitive hierarchy.
-
D.
promotionToPrimeiraLiga
Indicates that an entity (typically a football club) achieves promotion to compete in Portugal’s top-tier league, the Primeira Liga.
-
E.
hasPromotionToTopDivisionFrom
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 21, 2026, 1:30 p.m.