Triple
T17332402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Counties League |
E420847
|
entity |
| Predicate | hasMemberClubsType |
P18795
|
FINISHED |
| Object | non-league 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: non-league football clubs | Statement: [Combined Counties League, hasMemberClubsType, non-league football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberClubsType Context triple: [Combined Counties League, hasMemberClubsType, non-league football clubs]
-
A.
memberClubsType
chosen
Indicates that an entity is associated as a member with clubs of a specified type or category.
-
B.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
C.
hasMultiClubNetwork
Indicates that an entity is part of, or associated with, a network comprising multiple clubs under common ownership, management, or affiliation.
-
D.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
E.
refersToClubType
Indicates that one entity is associated with or designates a particular type or category of club.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a0fa57881909071fd395b3d46c4 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.