Triple
T8469191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neue Zeitschrift für Musik |
E200237
|
entity |
| Predicate | hasPublicationHistory |
P58089
|
FINISHED |
| Object | 19th century to present |
—
|
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: 19th century to present | Statement: [Neue Zeitschrift für Musik, hasPublicationHistory, 19th century to present]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicationHistory Context triple: [Neue Zeitschrift für Musik, hasPublicationHistory, 19th century to present]
-
A.
hasPublisherHistory
Indicates that there exists a record of past or current publishing relationships associated with the entity.
-
B.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
C.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
D.
hasHistoryNote
Indicates that there is an associated historical note or record describing past events, changes, or context related to the subject.
-
E.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d5dd088190a79050417f527f14 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.