Triple
T2679922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osiris myth |
E56548
|
entity |
| Predicate | roleOfHorus |
P9987
|
FINISHED |
| Object | avenger of his father |
—
|
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: avenger of his father | Statement: [Osiris myth, roleOfHorus, avenger of his father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfHorus Context triple: [Osiris myth, roleOfHorus, avenger of his father]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
E.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
- 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_69ab4a4b13fc81909dfdb3f23da46832 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abda2f7bf88190a1e3103dd014d871 |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd81ab9d08190b72b6104c6dbc769 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.