Triple
T14628926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Game |
E343426
|
entity |
| Predicate | coversCompetitionType |
P115103
|
FINISHED |
| Object | domestic 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: domestic football | Statement: [The Game, coversCompetitionType, domestic football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversCompetitionType Context triple: [The Game, coversCompetitionType, domestic football]
-
A.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
B.
overseesCompetitionType
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
-
C.
appliesToCompetition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a competition.
-
D.
supportsCompetition
Indicates that one entity actively promotes, enables, or upholds the existence or functioning of competition involving another entity.
-
E.
coveredCompetition
Indicates that an entity reported on, documented, or provided media coverage of a particular competition or contest.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.