Triple
T32392378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lansdowne Symphony Orchestra |
E827706
|
entity |
| Predicate | typicalPerformanceVenueType |
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: [Lansdowne Symphony Orchestra, typicalPerformanceVenueType, concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceVenueType Context triple: [Lansdowne Symphony Orchestra, typicalPerformanceVenueType, concert hall]
-
A.
hasPerformanceVenueType
chosen
Indicates that an entity is associated with, or classified by, a particular type of performance venue.
-
B.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
C.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
D.
typicalPerformanceOccasion
Indicates the usual or characteristic type of occasion, event, or context in which a performance typically takes place.
-
E.
typicalPerformanceFor
Indicates the usual or characteristic level of performance associated with a given entity, context, or condition.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:52 a.m.