Triple
T31788044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Amenemope |
E811383
|
entity |
| Predicate | hasAssociatedDeities |
P116883
|
FINISHED |
| Object | Osiris |
—
|
NE NERFINISHED |
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: Osiris | Statement: [Tomb of Amenemope, hasAssociatedDeities, Osiris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedDeities Context triple: [Tomb of Amenemope, hasAssociatedDeities, Osiris]
-
A.
hasDeities
chosen
Indicates that one entity possesses, is associated with, or is served by one or more deities.
-
B.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
D.
hasComponentDeity
Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
-
E.
sharesDeitiesWith
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 30, 2026, 11:38 p.m.