Triple
T35995042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGA Tour Tournament of Champions |
E1040957
|
entity |
| Predicate | startOfSeasonRole |
P47640
|
FINISHED |
| Object | season-opening tournament |
—
|
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: season-opening tournament | Statement: [PGA Tour Tournament of Champions, startOfSeasonRole, season-opening tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfSeasonRole Context triple: [PGA Tour Tournament of Champions, startOfSeasonRole, season-opening tournament]
-
A.
roleInSeason
chosen
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
B.
startSeason
Indicates the point in time or event at which a particular season begins.
-
C.
hasSeasonStructureRole
Indicates that an entity holds a specific functional or organizational role within a season-based structure or framework.
-
D.
originalSeasonStart
Indicates the date or point in time when a season (such as a sports league or TV series) first began or was originally launched.
-
E.
managerAtStartOfSeason
Indicates that a person holds the role of manager for a team or organization at the beginning of a specified season.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
Created at: May 3, 2026, 4:07 p.m.