Triple
T9857572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lublin Philharmonic |
E239624
|
entity |
| Predicate | hasPerformanceSpaceType |
P27770
|
FINISHED |
| Object | main 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: main concert hall | Statement: [Lublin Philharmonic, hasPerformanceSpaceType, main concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceSpaceType Context triple: [Lublin Philharmonic, hasPerformanceSpaceType, main concert hall]
-
A.
hasSpaceType
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
B.
performanceSpaceType
chosen
Indicates the specific kind or category of space in which a performance or event takes place.
-
C.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
D.
hasPerformanceLocation
Indicates that an event, performance, or show takes place at a specified location or venue.
-
E.
hasPerformanceContext
Indicates that an entity is associated with a specific performance-related situation, setting, or set of conditions under which it operates or is evaluated.
- 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_69ca84e6493081909cf58c8d42ea856b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb399bd8081908281d1735cc3909f |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:35 p.m.