Triple
T24902759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATP Challenger Tour |
E623622
|
entity |
| Predicate | typicalHostVenues |
P25526
|
FINISHED |
| Object | medium-sized tennis clubs |
—
|
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: medium-sized tennis clubs | Statement: [ATP Challenger Tour, typicalHostVenues, medium-sized tennis clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHostVenues Context triple: [ATP Challenger Tour, typicalHostVenues, medium-sized tennis clubs]
-
A.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
formerTypicalVenue
Indicates that a location was once the usual or primary venue for an entity’s activities or events, but no longer serves in that typical role.
-
C.
typicalVenueSetting
Indicates the usual or characteristic type of venue or setting in which an event, activity, or interaction typically takes place.
-
D.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
-
E.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
- 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_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 18, 2026, 5:27 a.m.