Triple
T27519004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EuroBasket 2017 MVP |
E694652
|
entity |
| Predicate | winnerLeagueAtTime |
P118835
|
FINISHED |
| Object | NBA |
—
|
NE NERFINISHED |
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: NBA | Statement: [EuroBasket 2017 MVP, winnerLeagueAtTime, NBA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerLeagueAtTime Context triple: [EuroBasket 2017 MVP, winnerLeagueAtTime, NBA]
-
A.
winnerLeagueAffiliationAtTime
chosen
Indicates that an entity is affiliated with a particular league at the time when it is the winner of a specified competition or event.
-
B.
notableLeagueEra
Indicates that the subject is significantly associated with, or best known for participating in, a particular era or period of a sports league.
-
C.
winnerLeagueDivision
Indicates that an entity has won a specific league division in a competitive context.
-
D.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
-
E.
historicLeagueStatus
Indicates that an entity’s league affiliation or classification applied in the past (historically), rather than reflecting its current league status.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 1:20 p.m.