Triple
T29468758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latvian Song and Dance Festival |
E747451
|
entity |
| Predicate | coreVenue |
P166905
|
FINISHED |
| Object | Mežaparks Great Bandstand |
—
|
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: Mežaparks Great Bandstand | Statement: [Latvian Song and Dance Festival, coreVenue, Mežaparks Great Bandstand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreVenue Context triple: [Latvian Song and Dance Festival, coreVenue, Mežaparks Great Bandstand]
-
A.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
B.
isCentralVenueOf
chosen
Indicates that a venue serves as the primary or main location for a specified event, organization, or activity.
-
C.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
D.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
E.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66ba94d588190b53154dfa3bbc52f |
completed | May 2, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:55 p.m.