Triple
T8517951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Dnipro |
E201621
|
entity |
| Predicate | playsIndoorSport |
P75342
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [BC Dnipro, playsIndoorSport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsIndoorSport Context triple: [BC Dnipro, playsIndoorSport, yes]
-
A.
playsInIndoorArena
chosen
Indicates that an entity participates or performs in an arena that is located indoors.
-
B.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
sportsInvolvement
Indicates the nature or extent of an entity’s participation in, association with, or role within a sport or sporting activity.
-
D.
isContactSport
Indicates that the activity involves significant physical contact between participants as an inherent and expected part of play.
-
E.
primarySport
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe626787c819087e72dd76b2d9310 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:15 p.m.