Triple
T1198906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PGA Championship |
E25731
|
entity |
| Predicate | previousPlayoffFormat |
P3749
|
FINISHED |
| Object | sudden-death playoff |
—
|
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: sudden-death playoff | Statement: [PGA Championship, previousPlayoffFormat, sudden-death playoff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPlayoffFormat Context triple: [PGA Championship, previousPlayoffFormat, sudden-death playoff]
-
A.
playoffStructure
chosen
Indicates how a competition’s postseason phase is organized, including the format, seeding, and progression of teams or players through playoff rounds.
-
B.
postseasonFormatChange
Indicates that the structure, rules, or qualification criteria of a postseason competition have been altered from a previous format.
-
C.
hasPlayOffs
Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
-
D.
previousFinals
Indicates that one entity represents a past or prior finals event or appearance in relation to another entity.
-
E.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9d56748190a12fe4a30346f1d8 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.