Triple
T29271978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | She Who Sees Horus and Seth |
E742142
|
entity |
| Predicate | refersToDeities |
P133801
|
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: [She Who Sees Horus and Seth, refersToDeities, Horus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToDeities Context triple: [She Who Sees Horus and Seth, refersToDeities, Horus]
-
A.
refersToDeityName
chosen
Indicates that one entity mentions, designates, or is associated with the name of a deity.
-
B.
refersToDeityFunction
Indicates that one entity denotes, describes, or points to the role, power, or functional aspect 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.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
E.
discussesDeity
Indicates that one entity talks or writes about, analyzes, or otherwise engages in discourse concerning a deity or divine being.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 28, 2026, 12:48 p.m.