Triple
T8881935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 10 in F-sharp major |
E211431
|
entity |
| Predicate | isFinalWorkOfType |
P61808
|
FINISHED |
| Object | final symphony by Gustav Mahler |
—
|
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: final symphony by Gustav Mahler | Statement: [Symphony No. 10 in F-sharp major, isFinalWorkOfType, final symphony by Gustav Mahler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFinalWorkOfType Context triple: [Symphony No. 10 in F-sharp major, isFinalWorkOfType, final symphony by Gustav Mahler]
-
A.
hasFinalFormUsage
Indicates that an entity is used or appears in its ultimate, completed, or final form within a given context or process.
-
B.
isOnlyBuiltWorkIn
Indicates that a work is the sole constructed work associated with a given location or context.
-
C.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
-
D.
hasFinalFormat
Indicates that an entity possesses or is associated with its completed, finalized version or representation.
-
E.
finalWorkInSeries
chosen
Indicates that one work is the concluding or last installment within a series of related works.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616a01f48190b8bbde0e898a38c7 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.