Triple
T26030342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V.League 1 |
E647412
|
entity |
| Predicate | governsClubParticipation |
P184574
|
FINISHED |
| Object | licensing and financial criteria |
—
|
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: licensing and financial criteria | Statement: [V.League 1, governsClubParticipation, licensing and financial criteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsClubParticipation Context triple: [V.League 1, governsClubParticipation, licensing and financial criteria]
-
A.
governsClub
Indicates that one entity holds governing authority or administrative control over a club.
-
B.
governsClubsFrom
Indicates that an entity has governing authority or administrative control over clubs originating from or associated with a specified source or location.
-
C.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
-
D.
includesClubLevel
Indicates that one entity encompasses or provides access to a specific club-level tier, area, or privileges associated with another entity.
-
E.
hasClubParticipantsType
Indicates the type or category of participants involved in a club.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.