Triple
T14938145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Paraders |
E372449
|
entity |
| Predicate | describesClubType |
P19215
|
FINISHED |
| Object | 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: professional football club | Statement: [The Paraders, describesClubType, professional football club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesClubType Context triple: [The Paraders, describesClubType, professional football club]
-
A.
memberClubsType
Indicates that an entity is associated as a member with clubs of a specified type or category.
-
B.
refersToClubType
chosen
Indicates that one entity is associated with or designates a particular type or category of club.
-
C.
clubMembershipType
Indicates the specific category or level of membership that an entity holds within a club.
-
D.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
E.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:38 a.m.