Triple
T30690781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahms symphony recordings with the Cleveland Orchestra |
E781320
|
entity |
| Predicate | historicalEraOfRecording |
P22765
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Brahms symphony recordings with the Cleveland Orchestra, historicalEraOfRecording, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfRecording Context triple: [Brahms symphony recordings with the Cleveland Orchestra, historicalEraOfRecording, 20th century]
-
A.
recordingEra
chosen
Indicates the historical time period or era during which the recording was made.
-
B.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
C.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
D.
recordingFormatEra
Indicates the historical time period or era associated with the recording format used for an audio or video recording.
-
E.
historicalEraOfNaming
Indicates the historical era or time period during which an entity received its name.
- 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_69f224ab24e08190991d6edb6df58e8b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: April 29, 2026, 8:33 p.m.