Triple
T22885877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference Premier |
E567602
|
entity |
| Predicate | containsClubsOfType |
P18795
|
FINISHED |
| Object | professional football clubs |
—
|
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: professional football clubs | Statement: [Conference Premier, containsClubsOfType, professional football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsClubsOfType Context triple: [Conference Premier, containsClubsOfType, professional football clubs]
-
A.
refersToClubType
Indicates that one entity is associated with or designates a particular type or category of club.
-
B.
includesInvitedClubs
Indicates that certain clubs are explicitly included among those invited to participate in a given event or context.
-
C.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
-
D.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
E.
memberClubsType
chosen
Indicates that an entity is associated as a member with clubs of a specified type or category.
- 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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc0cdb081908107d40069d9735f |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.