Triple
T25470736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odense Symphony Orchestra |
E638295
|
entity |
| Predicate | hasPerformanceVenueType |
P164990
|
FINISHED |
| Object | concert hall |
—
|
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: concert hall | Statement: [Odense Symphony Orchestra, hasPerformanceVenueType, concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceVenueType Context triple: [Odense Symphony Orchestra, hasPerformanceVenueType, concert hall]
-
A.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
B.
hasQualifyingVenue
Indicates that an entity is associated with a venue that meets specified qualifying criteria or standards.
-
C.
hasVenueComponentType
Indicates that a venue is associated with a specific type of component or functional part it contains or comprises.
-
D.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
-
E.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
- F. None of above. chosen
Provenance (4 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 21, 2026, 2:22 p.m.