Triple
T19256140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Muse |
E481520
|
entity |
| Predicate | functionInEpicPoetry |
P20800
|
FINISHED |
| Object | to authorize the poet’s narrative |
—
|
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: to authorize the poet’s narrative | Statement: [the Muse, functionInEpicPoetry, to authorize the poet’s narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInEpicPoetry Context triple: [the Muse, functionInEpicPoetry, to authorize the poet’s narrative]
-
A.
hasPoeticEpigraphs
Indicates that one entity (typically a work) includes poetic epigraphs associated with or prefacing another entity.
-
B.
epic
Indicates that an entity is characterized as grand, heroic, or extraordinarily impressive in scale, style, or impact.
-
C.
hasFeatureInPoem
Indicates that a poem includes or is characterized by a particular feature, element, or attribute.
-
D.
dramaticFunction
chosen
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
E.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3572c08190a55f1c71cdb18b42 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.