Triple
T38220486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korać Cup |
E1010794
|
entity |
| Predicate | successorCompetitionOrganizer |
P150191
|
FINISHED |
| Object | ULEB |
—
|
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: ULEB | Statement: [Korać Cup, successorCompetitionOrganizer, ULEB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorCompetitionOrganizer Context triple: [Korać Cup, successorCompetitionOrganizer, ULEB]
-
A.
successorCompetition
Indicates that one competition directly follows another in sequence, serving as its successor in a series or timeline.
-
B.
subsequentOrganizer
chosen
Indicates that one organizer follows another in a sequence, coming later in the ordering or timeline of organizers.
-
C.
associatedCompetitionOrganizer
Indicates that an entity has a relationship with, or is linked to, the organizer responsible for a particular competition.
-
D.
predecessorOrganizer
Indicates that one organizer entity served in the organizing role before another organizer in a sequence of organizers.
-
E.
organizationSuccessor
Indicates that one organization is the direct successor or continuation of another organization, inheriting its role, functions, or identity over time.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: May 3, 2026, 4:30 p.m.