Triple
T32381778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian football leagues |
E827440
|
entity |
| Predicate | futsalTopDivision |
P65874
|
FINISHED |
| Object | Slovenian Futsal League |
—
|
NE NERFINISHED |
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: Slovenian Futsal League | Statement: [Slovenian football leagues, futsalTopDivision, Slovenian Futsal League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futsalTopDivision Context triple: [Slovenian football leagues, futsalTopDivision, Slovenian Futsal League]
-
A.
topDivisionFormat
Indicates the competitive or organizational format used in the highest (top) division of a league or competition.
-
B.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
C.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
D.
futsalCompetition
chosen
Indicates a competitive event or tournament in the sport of futsal involving participating teams or players.
-
E.
topDivisionMatchesHosted
Indicates that an entity has hosted matches in the highest-level division of a competition or league.
- F. None of above.
Provenance (3 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1cb5598819081094ec74ca36bfa |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:51 a.m.