Triple

T1188350
Position Surface form Disambiguated ID Type / Status
Subject U.S. Open (golf) E25298 entity
Predicate playoffFormatCurrent P3749 FINISHED
Object two-hole aggregate 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: two-hole aggregate playoff | Statement: [U.S. Open (golf), playoffFormatCurrent, two-hole aggregate playoff]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: playoffFormatCurrent
Context triple: [U.S. Open (golf), playoffFormatCurrent, two-hole aggregate 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. playoffRound
    Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
  • C. playoffName
    Indicates the designated name or title assigned to a specific playoff series, round, or event within a competition.
  • D. hasPlayOffs
    Indicates that a competition, league, or season includes a playoff stage to determine final rankings or a champion.
  • E. playoffQualification
    Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
  • 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_69a49427d98881908646d6c63b8cea1e completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bd568cf481908d10cf19a3ce28f3 completed March 1, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69a4bb5bacc481909e8dfd5215e4711a completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:45 p.m.