Triple

T34697803
Position Surface form Disambiguated ID Type / Status
Subject World’s Largest Outdoor Cocktail Party E891077 entity
Predicate rivalryNameUsedByMedia P164548 FINISHED
Object World’s Largest Outdoor Cocktail Party NE NERFINISHED

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: World’s Largest Outdoor Cocktail Party | Statement: [World’s Largest Outdoor Cocktail Party, rivalryNameUsedByMedia, World’s Largest Outdoor Cocktail Party]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rivalryNameUsedByMedia
Context triple: [World’s Largest Outdoor Cocktail Party, rivalryNameUsedByMedia, World’s Largest Outdoor Cocktail Party]
  • A. rivalryName
    Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
  • B. rivalryNamedAfter
    Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
  • C. rivalNickname chosen
    Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
  • D. rivalryFocus
    Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
  • E. rivalryBasis
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • 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_69f349db7ab8819086808e833f472871 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f72ad38a208190b4bdc828297f86ad completed May 3, 2026, 11 a.m.
PD Predicate disambiguation batch_69f72a0243988190a43b8ea22457cd30 completed May 3, 2026, 10:57 a.m.
Created at: May 1, 2026, 2:05 a.m.