Triple
T24105116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA Zones |
E597197
|
entity |
| Predicate | useCompetitionSystem |
P13495
|
FINISHED |
| Object | FIBA competition calendar |
—
|
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 competition calendar | Statement: [FIBA Zones, useCompetitionSystem, FIBA competition calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useCompetitionSystem Context triple: [FIBA Zones, useCompetitionSystem, FIBA competition calendar]
-
A.
usesCompetitionSystem
chosen
Indicates that an entity operates under or applies a particular competition system or format.
-
B.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive context.
-
C.
usesCompetitionCode
Indicates that one entity applies or references a specific competition code associated with another entity.
-
D.
usedInCompetition
Indicates that something is employed or utilized as part of a competition or contest.
-
E.
competitionSystem
Indicates the structured set of rules, formats, and procedures that govern how a competition is organized, conducted, and decided.
- 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_69e288c60f9c8190af948d7354aedbeb |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1de154388819084f5a3f2b139287a |
completed | April 29, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:01 p.m.