Triple
T24902735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Challenger Tour |
E623622
|
entity |
| Predicate | tournamentCategories |
P53839
|
FINISHED |
| Object | Challenger 175 |
—
|
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: Challenger 175 | Statement: [ATP Challenger Tour, tournamentCategories, Challenger 175]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentCategories Context triple: [ATP Challenger Tour, tournamentCategories, Challenger 175]
-
A.
notableTournamentCategory
Indicates that an entity is associated with a tournament that is particularly notable or significant within a specified category or type.
-
B.
trophyCategory
Indicates the classification or type of award or trophy that an entity is associated with.
-
C.
playsCategory
Indicates that an entity engages in or performs activities belonging to a specified category.
-
D.
hasCompetitionCategory
chosen
Indicates that an entity is associated with a specific category or division within a competition.
-
E.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:27 a.m.