Triple
T28598779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ioannis Bourousis |
E723848
|
entity |
| Predicate | leagueSpecialization |
P153210
|
FINISHED |
| Object | European club 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: European club basketball | Statement: [Ioannis Bourousis, leagueSpecialization, European club basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueSpecialization Context triple: [Ioannis Bourousis, leagueSpecialization, European club basketball]
-
A.
teamSpecialty
Indicates the particular area of expertise or focus that characterizes a team’s skills or activities.
-
B.
teamEventSpecialty
Indicates that a team event is associated with a particular specialty, discipline, or specific type of competitive focus.
-
C.
hasSportSpecialty
Indicates that an entity has a particular sport in which it specializes or is primarily associated.
-
D.
uniformSpecialty
Indicates that multiple entities share the same specific specialty, expertise, or area of focus.
-
E.
leagueSport
chosen
Indicates that a particular sport is the official or primary sport associated with a given league.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 4:23 a.m.