Triple
T33721412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBSL |
E864025
|
entity |
| Predicate | memberClubsParticipateIn |
P154119
|
FINISHED |
| Object | EuroLeague |
—
|
NE NERFINISHED |
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: EuroLeague | Statement: [IBSL, memberClubsParticipateIn, EuroLeague]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberClubsParticipateIn Context triple: [IBSL, memberClubsParticipateIn, EuroLeague]
-
A.
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.
-
B.
memberClubsType
Indicates that an entity is associated as a member with clubs of a specified type or category.
-
C.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
-
D.
hadMemberClubsIn
Indicates that an organization or group possessed member clubs located within a specified place or jurisdiction.
-
E.
clubsParticipateIn
chosen
Indicates that one or more clubs take part in, are involved with, or are registered to participate in a particular event, activity, or competition.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 1, 2026, 1:44 a.m.