Triple
T35783714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokito Oda |
E1034504
|
entity |
| Predicate | competesOnTour |
P103151
|
FINISHED |
| Object | ITF Wheelchair Tennis Tour |
—
|
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: ITF Wheelchair Tennis Tour | Statement: [Tokito Oda, competesOnTour, ITF Wheelchair Tennis Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesOnTour Context triple: [Tokito Oda, competesOnTour, ITF Wheelchair Tennis Tour]
-
A.
playsOnTour
chosen
Indicates that an individual or group regularly performs as part of an organized tour or touring schedule.
-
B.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
C.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
D.
tourEvent
Indicates an event that is part of a tour, such as a scheduled stop, performance, or appearance within a larger touring itinerary.
-
E.
qualifyingCompetitionFor
Indicates that one competition serves as a qualifying event for participation in another competition.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:06 p.m.