Triple
T17369233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Counties League |
E422264
|
entity |
| Predicate | hasMemberClubType |
P18795
|
FINISHED |
| Object | semi-professional football club |
—
|
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: semi-professional football club | Statement: [United Counties League, hasMemberClubType, semi-professional football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberClubType Context triple: [United Counties League, hasMemberClubType, semi-professional football club]
-
A.
clubMembershipType
Indicates the specific category or level of membership that an entity holds within a club.
-
B.
hasMemberType
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
C.
hasMembershipBy
Indicates that an entity holds or acquires membership in a group, organization, or program by means of a specified agent, process, or instrument.
-
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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6842388190940235198fa50041 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.