Triple
T30906133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in h-Moll |
E787304
|
entity |
| Predicate | workCompletenessStatus |
P39444
|
FINISHED |
| Object | unfinished |
—
|
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: unfinished | Statement: [Sinfonie in h-Moll, workCompletenessStatus, unfinished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCompletenessStatus Context triple: [Sinfonie in h-Moll, workCompletenessStatus, unfinished]
-
A.
worksStatus
chosen
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
B.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
C.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
- 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_69f6927ecf6c81908f9a9b1380bc43fe |
completed | May 3, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:50 p.m.