Triple
T30906142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in h-Moll |
E787304
|
entity |
| Predicate | hasWorkNumbering |
P70295
|
FINISHED |
| Object | Symphony No. 8 |
—
|
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: Symphony No. 8 | Statement: [Sinfonie in h-Moll, hasWorkNumbering, Symphony No. 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkNumbering Context triple: [Sinfonie in h-Moll, hasWorkNumbering, Symphony No. 8]
-
A.
workNumbering
chosen
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
-
B.
hasWorkNumberType
Indicates that an entity’s work-related phone number is classified as a specific type (e.g., mobile, landline, extension).
-
C.
hasCategoryNumbering
Indicates that an entity is assigned or associated with a specific category-based numbering or index within a classification system.
-
D.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
E.
hasNumberingRole
Indicates that an entity holds a specific role or responsibility related to assigning, managing, or using numbers within a given context.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 29, 2026, 8:50 p.m.