Triple
T15448999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2002 FIBA World Championship MVP |
E370097
|
entity |
| Predicate | tournamentContinentScope |
P118838
|
FINISHED |
| Object | worldwide |
—
|
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: worldwide | Statement: [2002 FIBA World Championship MVP, tournamentContinentScope, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentContinentScope Context triple: [2002 FIBA World Championship MVP, tournamentContinentScope, worldwide]
-
A.
raceCalendarContinent
Indicates the continent on whose race calendar a particular race or racing event is scheduled.
-
B.
notableTournamentRegion
Indicates that a tournament is notably associated with, recognized in, or significant within a particular geographic region.
-
C.
continentalCompetition
Indicates a competitive relationship or event that takes place at, or is organized across, the level of an entire continent.
-
D.
continentScope
Indicates that something applies within, is limited to, or is defined at the level of a specific continent.
-
E.
continentOfParticipatingTeams
Indicates the continent from which the participating teams in an event or competition originate.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ef9334c81908541e231b43eb012 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.