Triple
T28670713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Wheelchair Tennis Tour |
E725709
|
entity |
| Predicate | hasTournamentLocationScope |
P15208
|
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: [ITF Wheelchair Tennis Tour, hasTournamentLocationScope, worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentLocationScope Context triple: [ITF Wheelchair Tennis Tour, hasTournamentLocationScope, worldwide]
-
A.
teamLocationScope
Indicates the geographic or organizational area within which a team operates or is considered relevant.
-
B.
hasTournamentLevel
Indicates that an entity participates in or is classified by a specific competitive or organizational level within a tournament structure.
-
C.
hasCompetitionScope
chosen
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
D.
isTopLevelTournamentFor
Indicates that a tournament is the highest or primary competitive event associated with a given entity (such as a league, sport, or organization).
-
E.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 5:03 a.m.