Triple
T29576070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blumine |
E753445
|
entity |
| Predicate | firstPerformanceAsPartOfSymphony |
P203033
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Blumine, firstPerformanceAsPartOfSymphony, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceAsPartOfSymphony Context triple: [Blumine, firstPerformanceAsPartOfSymphony, late 19th century]
-
A.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
B.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
C.
firstPerformance
Indicates that an entity marks the initial or debut performance of another entity, such as a work, artist, or production.
-
D.
firstPerformanceWork
Indicates that a performance is the debut or initial presentation of a particular work.
-
E.
firstConcertoComposed
Indicates that the subject is the first concerto ever composed by, or attributed to, the object.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_6a0117b4eec88190a761ac126f5cc8e2 |
completed | May 10, 2026, 11:41 p.m. |
Created at: April 28, 2026, 6:03 p.m.