Triple
T32882951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 7 "Sinfonia antartica" |
E841115
|
entity |
| Predicate | epigraphAuthors |
P84429
|
FINISHED |
| Object | various poets and writers |
—
|
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: various poets and writers | Statement: [Symphony No. 7 "Sinfonia antartica", epigraphAuthors, various poets and writers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epigraphAuthors Context triple: [Symphony No. 7 "Sinfonia antartica", epigraphAuthors, various poets and writers]
-
A.
bookAuthors
Indicates the relationship between a book and the person or people who authored it.
-
B.
hasPoeticEpigraphs
chosen
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
C.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
-
D.
authorOfForewordOrIntro
Indicates that one entity is the person who wrote the foreword or introduction for a work associated with the other entity.
-
E.
authorFounded
Indicates that the author is the person who established or created the referenced organization, institution, or 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.