Triple
T122266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference of Champions |
E2473
|
entity |
| Predicate | appliesToSports |
P5085
|
FINISHED |
| Object | basketball |
—
|
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: basketball | Statement: [Conference of Champions, appliesToSports, basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToSports Context triple: [Conference of Champions, appliesToSports, basketball]
-
A.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
numberOfSports
Indicates the quantity of distinct sports associated with or involved in a given entity.
-
C.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
D.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
E.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
- 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a2573b4e7481909ee09d2899f8a74b |
completed | Feb. 28, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69a2564928208190966a619680a0d6e2 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256c72f6c81909b619b90d829d86e |
completed | Feb. 28, 2026, 2:45 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.