Triple
T24902701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Rankings |
E623621
|
entity |
| Predicate | hasSpecialList |
P159700
|
FINISHED |
| Object | ATP Race to Turin |
—
|
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 Race to Turin | Statement: [ATP Rankings, hasSpecialList, ATP Race to Turin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialList Context triple: [ATP Rankings, hasSpecialList, ATP Race to Turin]
-
A.
hasSpecialistLists
Indicates that an entity maintains or is associated with one or more curated lists of specialists or specialized items.
-
B.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
C.
hasSpecials
Indicates that an entity offers or is associated with special deals, promotions, or limited-time offers.
-
D.
hasNumberOfSpecials
Indicates that an entity is associated with a specific count of special items, features, or occurrences.
-
E.
hasSpecialCategory
Indicates that an entity is associated with a designated special or exceptional category distinct from its standard classifications.
- 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_69e2fac797cc8190b30d77f4121099ac |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 5:27 a.m.