Triple
T18844417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carling Knockout Cup |
E460879
|
entity |
| Predicate | isProfessionalCompetition |
P133151
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Carling Knockout Cup, isProfessionalCompetition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isProfessionalCompetition Context triple: [Carling Knockout Cup, isProfessionalCompetition, true]
-
A.
isProfessionalLeague
Indicates that a sports league operates at a professional level, typically involving paid athletes and formal organizational structures.
-
B.
isCompetitive
Indicates that one entity engages in rivalry or competition with another, typically striving to outperform or win against it.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
officialCompetition
Indicates that there is a formally recognized or sanctioned competition relationship between the entities.
-
E.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ed944c81908592f0c34e5727a0 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:56 a.m.