Triple
T26398281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Super League |
E663631
|
entity |
| Predicate | hasClubParticipantsType |
P172097
|
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: [Chinese Super League, hasClubParticipantsType, professional football clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubParticipantsType Context triple: [Chinese Super League, hasClubParticipantsType, professional football clubs]
-
A.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
hasPlayersClub
Indicates that an entity operates, sponsors, or is associated with a players’ club or loyalty program for players.
-
C.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
D.
includesInvitedClubs
Indicates that certain clubs are explicitly included among those invited to participate in a given event or context.
-
E.
participatingClubsFrom
Indicates that certain clubs are taking part in or are involved in an event, activity, or context originating from a specified source or organizer.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 26, 2026, 11:30 p.m.