Triple
T24902688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Rankings |
E623621
|
entity |
| Predicate | governsTour |
P87747
|
FINISHED |
| Object | ITF Men’s World Tennis Tour (for ranking points) |
—
|
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 Men’s World Tennis Tour (for ranking points) | Statement: [ATP Rankings, governsTour, ITF Men’s World Tennis Tour (for ranking points)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsTour Context triple: [ATP Rankings, governsTour, ITF Men’s World Tennis Tour (for ranking points)]
-
A.
governingTour
chosen
Indicates that one entity conducts or oversees an official tour or guided visit for another entity.
-
B.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
C.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
D.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
E.
hasTourismAuthority
Indicates that an entity holds official responsibility or power to manage, regulate, or oversee tourism-related activities for another entity or area.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 18, 2026, 5:27 a.m.