Triple
T34697804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World’s Largest Outdoor Cocktail Party |
E891077
|
entity |
| Predicate | rivalryNameDiscouragedBy |
P180109
|
FINISHED |
| Object | Southeastern Conference |
—
|
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: Southeastern Conference | Statement: [World’s Largest Outdoor Cocktail Party, rivalryNameDiscouragedBy, Southeastern Conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryNameDiscouragedBy Context triple: [World’s Largest Outdoor Cocktail Party, rivalryNameDiscouragedBy, Southeastern Conference]
-
A.
rivalryNamedAfter
Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
-
B.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
rivalryStatus
Indicates a competitive or adversarial relationship between entities, often involving ongoing opposition or contention.
-
E.
rivalryCharacterizedBy
Indicates a relationship where a rivalry is defined or distinguished by a particular feature, quality, or circumstance.
- F. None of above. chosen
Provenance (4 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_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
| PDg | Predicate description generation | batch_69f731cbca10819091eefe2f2487928e |
completed | May 3, 2026, 11:30 a.m. |
Created at: May 1, 2026, 2:05 a.m.