Triple
T35288863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Day of the Lifting of the Siege of Leningrad ceremonies |
E1019166
|
entity |
| Predicate | formerlyHeldIn |
P149814
|
FINISHED |
| Object | Leningrad |
—
|
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: Leningrad | Statement: [Day of the Lifting of the Siege of Leningrad ceremonies, formerlyHeldIn, Leningrad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerlyHeldIn Context triple: [Day of the Lifting of the Siege of Leningrad ceremonies, formerlyHeldIn, Leningrad]
-
A.
formerVenueLocation
chosen
Indicates that a location previously served as the venue for an entity or event but no longer does so.
-
B.
formerVenueComponentOf
Indicates that a venue previously functioned as a component or part of a larger venue or venue complex, but no longer holds that status.
-
C.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
D.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
E.
originallyHostedBy
Indicates that something (such as an event, program, or content) was first hosted or carried by a particular host or platform before any subsequent changes.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
Created at: May 3, 2026, 4:03 p.m.