Triple
T32381753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian football leagues |
E827440
|
entity |
| Predicate | includeCompetitionType |
P115103
|
FINISHED |
| Object | men's football |
—
|
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: men's football | Statement: [Slovenian football leagues, includeCompetitionType, men's football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeCompetitionType Context triple: [Slovenian football leagues, includeCompetitionType, men's football]
-
A.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
B.
associatedCompetitionType
Indicates that one entity is linked to or involved with a particular type or category of competition.
-
C.
coversCompetitionType
chosen
Indicates that one entity includes or addresses a particular type or category of competition.
-
D.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
E.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
- 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_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
Created at: May 1, 2026, 12:51 a.m.