Triple
T30592446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1981 Stanley Cup Finals |
E778696
|
entity |
| Predicate | cityChampionVenue |
P19642
|
FINISHED |
| Object | Uniondale, New York |
—
|
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: Uniondale, New York | Statement: [1981 Stanley Cup Finals, cityChampionVenue, Uniondale, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityChampionVenue Context triple: [1981 Stanley Cup Finals, cityChampionVenue, Uniondale, New York]
-
A.
cityOfVenue
chosen
Indicates the city in which a given venue is located.
-
B.
isCentralVenueOf
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
C.
typicalVenueCity
Indicates that a particular city is the usual or standard location where an event, activity, or organization is typically held or based.
-
D.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
E.
notableVenueFor
Indicates that a venue is especially recognized or significant for hosting, presenting, or being associated with a particular entity or activity.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6897bc52481908122b1af6cb45526 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.