Triple
T21054528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly Muse |
E518674
|
entity |
| Predicate | epicFunction |
P142662
|
FINISHED |
| Object | to authorize the poem’s truth-claims |
—
|
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 poem’s truth-claims | Statement: [Heavenly Muse, epicFunction, to authorize the poem’s truth-claims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epicFunction Context triple: [Heavenly Muse, epicFunction, to authorize the poem’s truth-claims]
-
A.
epic
Indicates that an entity is characterized as grand, heroic, or extraordinarily impressive in scale, style, or impact.
-
B.
epicBattle
Indicates a large-scale, intense conflict or confrontation between opposing entities, often marked by extraordinary stakes or dramatic significance.
-
C.
majorEpic
Indicates that an entity is a principal or most significant epic work associated with another entity (such as an author, tradition, or corpus).
-
D.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
E.
peakFunction
Indicates that a function reaches a maximum (peak) value at a specific point or over a given interval.
- F. None of above. chosen
Provenance (4 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7edb8481908e4dc7573f7fa98f |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf9d71881908cd85dfc37db93ca |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:36 p.m.