Triple
T22018392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 8 in C minor |
E543771
|
entity |
| Predicate | typicalEdition |
P101738
|
FINISHED |
| Object | Haas edition |
—
|
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: Haas edition | Statement: [Symphony No. 8 in C minor, typicalEdition, Haas edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEdition Context triple: [Symphony No. 8 in C minor, typicalEdition, Haas edition]
-
A.
laterTypicalEditionYear
Indicates that one edition’s typical publication year occurs after that of another edition.
-
B.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
C.
editionPattern
Indicates a recurring structure or template that characterizes how different editions or versions of something are organized or produced.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalItem
chosen
Indicates that an item is a representative or characteristic example of a broader category, class, or set.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c5929881908458d07bd33c5edd |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.