Triple
T27297599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ka-nakht-mery-Maat |
E688809
|
entity |
| Predicate | bearsTheophoricReference |
P9869
|
FINISHED |
| Object | Horus |
—
|
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: Horus | Statement: [Ka-nakht-mery-Maat, bearsTheophoricReference, Horus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearsTheophoricReference Context triple: [Ka-nakht-mery-Maat, bearsTheophoricReference, Horus]
-
A.
isTheophoric
chosen
Indicates that something (typically a name or term) incorporates the name of a deity or refers explicitly to a god.
-
B.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
C.
usesTheonym
Indicates that one entity refers to or designates another entity by using a theonym, i.e., the proper name of a deity.
-
D.
typicalNameBearers
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
-
E.
usedAsNamesakeFor
Indicates that one entity serves as the source or inspiration for the name given to another entity.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62781a37c8190aa99f316b45ef952 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:19 a.m.