Triple
T32535765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier 5 tournaments |
E831583
|
entity |
| Predicate | tournamentCalendarPosition |
P44231
|
FINISHED |
| Object | spread across season |
—
|
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: spread across season | Statement: [Premier 5 tournaments, tournamentCalendarPosition, spread across season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentCalendarPosition Context triple: [Premier 5 tournaments, tournamentCalendarPosition, spread across season]
-
A.
typicalCalendarPosition
chosen
Indicates the usual or standard placement of something within a calendar sequence, such as its customary date, time, or ordering.
-
B.
competitionCalendar
Indicates that there is a scheduled set of competitive events or matches associated with an entity over a defined period.
-
C.
tournamentBracket
Indicates the structured competitive relationship among participants in a tournament, showing who faces whom and how winners advance through successive rounds.
-
D.
tourEvent
Indicates an event that is part of a tour, such as a scheduled stop, performance, or appearance within a larger touring itinerary.
-
E.
tournamentUse
Indicates that a tournament utilizes or is conducted using a particular resource, format, rule set, or venue.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:01 a.m.