Triple
T22942285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Symphony of Three Orchestras |
E569765
|
entity |
| Predicate | intendedVenueType |
P10640
|
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: [A Symphony of Three Orchestras, intendedVenueType, concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedVenueType Context triple: [A Symphony of Three Orchestras, intendedVenueType, concert hall]
-
A.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
C.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
D.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
E.
home venue type
Indicates the kind or category of place that serves as the primary location where an entity regularly hosts its events or activities.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819a509481908a3662ef80f757c7 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.