Triple
T27127441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovar Supercup |
E681468
|
entity |
| Predicate | openingFixtureOf |
P85027
|
FINISHED |
| Object | Kosovar football season |
—
|
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: Kosovar football season | Statement: [Kosovar Supercup, openingFixtureOf, Kosovar football season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingFixtureOf Context triple: [Kosovar Supercup, openingFixtureOf, Kosovar football season]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
C.
openingFunction
Indicates that one entity serves as the initial or primary function, role, or operation that begins or initiates a process, sequence, or interaction involving another entity.
-
D.
openingBegan
Indicates that the process of opening something has started.
-
E.
openingStage
chosen
Indicates the initial phase or first part of a process, event, or sequence in which subsequent stages will follow.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 9:02 a.m.