Triple
T22452308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIBA competitions |
E555023
|
entity |
| Predicate | rankingFunction |
P7476
|
FINISHED |
| Object | determine FIBA World Rankings |
—
|
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: determine FIBA World Rankings | Statement: [FIBA competitions, rankingFunction, determine FIBA World Rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingFunction Context triple: [FIBA competitions, rankingFunction, determine FIBA World Rankings]
-
A.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
B.
rankFunctionCharacterization
Indicates that a function is being characterized or defined in terms of its rank, typically specifying how the rank property determines or describes the function’s behavior or classification.
-
C.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
D.
rankingBasis
chosen
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
E.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4c63e88190aeedc326599edd18 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.