Triple
T31999886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roussel symphonies |
E817093
|
entity |
| Predicate | primaryPerformanceVenueType |
P206143
|
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: [Roussel symphonies, primaryPerformanceVenueType, concert hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPerformanceVenueType Context triple: [Roussel symphonies, primaryPerformanceVenueType, concert hall]
-
A.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
C.
hasPerformanceVenueType
Indicates that an entity is associated with, or classified by, a particular type of performance venue.
-
D.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
E.
originalPerformanceVenue
Indicates the venue where a performance was first originally presented or premiered.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:14 a.m.