Triple
T26806047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian Cup |
E671838
|
entity |
| Predicate | stageOfEntryForTopDivisionClubs |
P162822
|
FINISHED |
| Object | later rounds |
—
|
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: later rounds | Statement: [Belgian Cup, stageOfEntryForTopDivisionClubs, later rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageOfEntryForTopDivisionClubs Context triple: [Belgian Cup, stageOfEntryForTopDivisionClubs, later rounds]
-
A.
levelInUEFASystem
Indicates the specific tier or division an entity occupies within the hierarchical structure of the UEFA football league system.
-
B.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
C.
levelBeforeDivisionI
Indicates the competitive level or tier at which an entity participated prior to moving into Division I.
-
D.
qualificationFromTopDivision
Indicates that an entity has earned qualification originating from the highest (top) competitive division in a given hierarchy or system.
-
E.
championLeagueLevel
Indicates the competitive tier or division of a league in which a champion or team competes.
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62e4168a48190b45268f922780da6 |
completed | May 2, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d5268ac8190835dc7119353b840 |
completed | May 2, 2026, 4:58 p.m. |
Created at: April 27, 2026, 4:26 a.m.