Triple
T30879732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haydn symphonies |
E786577
|
entity |
| Predicate | catalogueRange |
P132517
|
FINISHED |
| Object | Hob. I:1–Hob. I:104 |
—
|
NE NERFINISHED |
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: Hob. I:1–Hob. I:104 | Statement: [Haydn symphonies, catalogueRange, Hob. I:1–Hob. I:104]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueRange Context triple: [Haydn symphonies, catalogueRange, Hob. I:1–Hob. I:104]
-
A.
categoryRange
chosen
Indicates that a category or classification spans from a defined lower bound to an upper bound within a specified range.
-
B.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
D.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
E.
articleNumberRange
Indicates that something is associated with or falls within a specified range of article numbers.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:48 p.m.