Triple
T26761627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Club |
E674816
|
entity |
| Predicate | tournamentTiming |
P79963
|
FINISHED |
| Object | pre-Wimbledon |
—
|
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: pre-Wimbledon | Statement: [Queen's Club, tournamentTiming, pre-Wimbledon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentTiming Context triple: [Queen's Club, tournamentTiming, pre-Wimbledon]
-
A.
competitionTiming
chosen
Indicates the temporal relationship or scheduling of when a competition or competitive event takes place.
-
B.
tournamentSpecific
Indicates that the relationship, condition, or data applies only within the context of a particular tournament and not generally across other contexts or events.
-
C.
tourEvent
Indicates an event that is part of a tour, such as a scheduled stop, performance, or appearance within a larger touring itinerary.
-
D.
tournamentMatches
Indicates that a tournament includes or schedules specific matches as part of its competitive structure.
-
E.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:58 a.m.