Triple
T22503053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsumoto Performing Arts Centre |
E556322
|
entity |
| Predicate | typeOfEventsHosted |
P58154
|
FINISHED |
| Object | orchestral 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: orchestral concerts | Statement: [Matsumoto Performing Arts Centre, typeOfEventsHosted, orchestral concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEventsHosted Context triple: [Matsumoto Performing Arts Centre, typeOfEventsHosted, orchestral concerts]
-
A.
hostsTypeOfEvent
chosen
Indicates that an entity organizes or provides the venue for a particular type or category of event.
-
B.
alsoHostedEventType
Indicates that the same host was responsible for organizing or holding another event of a specified type.
-
C.
festivalTypeHosted
Indicates that a particular location or organizer hosts festivals of a specified type.
-
D.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
-
E.
eventTypeOrganized
Indicates that an entity organized or arranged a specific type or category of 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5a01888190ba65a05616b63cbe |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.