Triple
T3587089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Elba, New York |
E75935
|
entity |
| Predicate | hasMajorEventSite |
P7849
|
FINISHED |
| Object | 1932 Winter Olympics venues |
—
|
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: 1932 Winter Olympics venues | Statement: [North Elba, New York, hasMajorEventSite, 1932 Winter Olympics venues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorEventSite Context triple: [North Elba, New York, hasMajorEventSite, 1932 Winter Olympics venues]
-
A.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
B.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
C.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
D.
hasCapitalSite
Indicates that a political or administrative entity has a specific place designated as its capital location.
-
E.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc137eb708190809cd52b6deb227c |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.