Triple
T30916366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP |
E787588
|
entity |
| Predicate | hasTourCategory |
P51013
|
FINISHED |
| Object | ATP Tour Masters 1000 |
—
|
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: ATP Tour Masters 1000 | Statement: [ATP, hasTourCategory, ATP Tour Masters 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourCategory Context triple: [ATP, hasTourCategory, ATP Tour Masters 1000]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
C.
hasTourAccess
Indicates that an entity is permitted to enter or participate in a specified tour.
-
D.
hasTicketCategory
Indicates that an item, event, or access right is associated with a specific ticket category or type.
-
E.
tourCategory
chosen
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 8:51 p.m.