Triple
T22634463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opheltes (Archemorus) |
E558641
|
entity |
| Predicate | meaningOfNameArchemorus |
P35820
|
FINISHED |
| Object | beginning of doom |
—
|
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: beginning of doom | Statement: [Opheltes (Archemorus), meaningOfNameArchemorus, beginning of doom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfNameArchemorus Context triple: [Opheltes (Archemorus), meaningOfNameArchemorus, beginning of doom]
-
A.
ancientNameMeaning
Indicates that an entity’s ancient or historical name carries a particular meaning or interpretation.
-
B.
speciesNameMeaning
Indicates the meaning or etymological sense of a species’ scientific name.
-
C.
genusNameMeaning
Indicates the meaning or etymological sense of the name of a genus.
-
D.
heroNameMeaning
chosen
Indicates that a hero’s name has a particular meaning, interpretation, or etymological significance.
-
E.
equivalentMythologicalName
Indicates that two entities share the same identity in mythology, representing different names or versions of the same mythological figure.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1700be10c8190830393fdbec1033d |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:03 p.m.