Triple
T28298308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let the bright seraphim |
E713630
|
entity |
| Predicate | typicalPerformanceFor |
P202403
|
FINISHED |
| Object | concert repertoire |
—
|
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 repertoire | Statement: [Let the bright seraphim, typicalPerformanceFor, concert repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceFor Context triple: [Let the bright seraphim, typicalPerformanceFor, concert repertoire]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
-
C.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
D.
typicalPerformanceForces
Indicates the forces that are normally or characteristically exerted or experienced during a given type of performance or operation.
-
E.
typicalPerformanceOccasion
Indicates the usual or characteristic type of occasion, event, or context in which a performance typically takes place.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
| PDg | Predicate description generation | batch_6a007aa82810819080bb16dd5022c324 |
completed | May 10, 2026, 12:31 p.m. |
Created at: April 27, 2026, 11:33 p.m.