Triple
T23528958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA European Champions Cup |
E576508
|
entity |
| Predicate | organiserUntil |
P153126
|
FINISHED |
| Object | FIBA until 2000–01 |
—
|
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: FIBA until 2000–01 | Statement: [FIBA European Champions Cup, organiserUntil, FIBA until 2000–01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organiserUntil Context triple: [FIBA European Champions Cup, organiserUntil, FIBA until 2000–01]
-
A.
lastOrganizer
Indicates that one entity is the most recent or final organizer associated with another entity or event.
-
B.
organisedFor
Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
-
C.
organisedSince
Indicates that an entity has been formally organized or established starting from a specified point in time.
-
D.
subsequentOrganizer
Indicates that one organizer follows another in a sequence, coming later in the ordering or timeline of organizers.
-
E.
organisedWith
Indicates that two or more entities are arranged, coordinated, or structured together as part of the same organizing context or effort.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac7646a48190b5dcbaf8c0c194df |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:09 p.m.