Triple
T14477993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encomium of Helen |
E359023
|
entity |
| Predicate | listsCauseOfHelenAction |
P63894
|
FINISHED |
| Object | will of the gods |
—
|
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: will of the gods | Statement: [Encomium of Helen, listsCauseOfHelenAction, will of the gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsCauseOfHelenAction Context triple: [Encomium of Helen, listsCauseOfHelenAction, will of the gods]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
ElizabethAction
Indicates that Elizabeth performs, initiates, or is responsible for a particular action or activity in relation to other entities.
-
C.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
D.
hasCauseNarrative
chosen
Indicates that one entity provides a narrative or explanatory account of the cause or causal background of another entity or event.
-
E.
causeOfDownfall
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.