Triple
T28670663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Seniors Tour |
E725708
|
entity |
| Predicate | hasTournamentLevel |
P179485
|
FINISHED |
| Object | Grade A |
—
|
LITERAL FINISHED |
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: Grade A | Statement: [ITF Seniors Tour, hasTournamentLevel, Grade A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentLevel Context triple: [ITF Seniors Tour, hasTournamentLevel, Grade A]
-
A.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
B.
isTopLevelTournamentFor
Indicates that a tournament is the highest or primary competitive event associated with a given entity (such as a league, sport, or organization).
-
C.
hasTournamentType
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
-
D.
qualifiedForTournament
Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
-
E.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 5:03 a.m.