Triple
T24902489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix tennis circuit |
E623617
|
entity |
| Predicate | includedTournaments |
P48631
|
FINISHED |
| Object | Grand Prix Super Series events |
—
|
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: Grand Prix Super Series events | Statement: [Grand Prix tennis circuit, includedTournaments, Grand Prix Super Series events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedTournaments Context triple: [Grand Prix tennis circuit, includedTournaments, Grand Prix Super Series events]
-
A.
includesConferenceTournaments
Indicates that the subject entity encompasses or accounts for conference tournaments as part of its scope, structure, or content.
-
B.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
C.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
-
D.
numberOfTournaments
Indicates the total count of tournaments associated with or participated in by an entity.
-
E.
includesCompetition
chosen
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
- 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_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 18, 2026, 5:27 a.m.