Triple
T36452629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1924 Horus |
E898052
|
entity |
| Predicate | namedAfterDeityFrom |
P45679
|
FINISHED |
| Object | ancient Egyptian mythology |
—
|
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: ancient Egyptian mythology | Statement: [1924 Horus, namedAfterDeityFrom, ancient Egyptian mythology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterDeityFrom Context triple: [1924 Horus, namedAfterDeityFrom, ancient Egyptian mythology]
-
A.
namedAfterDeity
chosen
Indicates that one entity has been given a name derived from or in honor of a deity.
-
B.
refersToDeityName
Indicates that one entity mentions, designates, or is associated with the name of a deity.
-
C.
roleOfReferencedDeity
Indicates that one entity specifies the function, status, or position held by a deity that is referenced in relation to another entity or context.
-
D.
veneratedDeityNameVariant
Indicates that the referenced name is an alternative or variant form used to venerate or refer to a particular deity.
-
E.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:10 p.m.