Triple
T35133163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampere Hall |
E1014496
|
entity |
| Predicate | significantEventTypeHosted |
P51476
|
FINISHED |
| Object | classical music concerts |
—
|
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: classical music concerts | Statement: [Tampere Hall, significantEventTypeHosted, classical music concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventTypeHosted Context triple: [Tampere Hall, significantEventTypeHosted, classical music concerts]
-
A.
notableEventHostedAtReferredVenue
Indicates that a notable event was hosted at, or took place in, the referenced venue.
-
B.
significantEventType
chosen
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
countryHostedEvent
Indicates that a specific country served as the host location for a particular event.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.