Triple
T32882950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 7 "Sinfonia antartica" |
E841115
|
entity |
| Predicate | hasTextualEpigraphs |
P84429
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Symphony No. 7 "Sinfonia antartica", hasTextualEpigraphs, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTextualEpigraphs Context triple: [Symphony No. 7 "Sinfonia antartica", hasTextualEpigraphs, true]
-
A.
hasPoeticEpigraphs
chosen
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
B.
hasSacredText
Indicates that an entity possesses or is associated with a particular sacred or religious text.
-
C.
hasTextualTransmission
Indicates that a work, idea, or content has been passed down, preserved, or conveyed through written or textual forms over time.
-
D.
epigraphicType
Indicates the specific kind or category of an inscription as classified in epigraphic studies.
-
E.
hasEpilogueBy
Indicates that an epilogue of a work is authored, written, or created by a specified agent.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:18 a.m.