Triple
T12156481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seth |
E289585
|
entity |
| Predicate | fought |
P30824
|
FINISHED |
| Object | Apophis |
E964986
|
NE 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: Apophis | Statement: [Seth, fought, Apophis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Apophis Context triple: [Seth, fought, Apophis]
-
A.
Apophis
chosen
Apophis is the giant serpent-shaped embodiment of chaos in ancient Egyptian mythology, eternally battling the sun god Ra and threatening the cosmic order.
-
B.
Horus
Horus is a major ancient Egyptian sky and kingship god, often depicted as a falcon or falcon-headed man and closely associated with divine rulership and protection.
-
C.
Abraxas
Abraxas is a mystical term originating in Gnostic traditions, often used as a name for a powerful, transcendent deity or symbolic figure representing the union of opposites.
-
D.
Kheperkara
Kheperkara is the throne name of the ancient Egyptian pharaoh Senusret I of the Twelfth Dynasty.
-
E.
Serapis
Serapis is a Greco-Egyptian syncretic god combining aspects of Osiris and Apis with Hellenistic deities, worshipped widely in the Ptolemaic and Roman worlds.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915c1673c8190830cd15525d16869 |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60a80aa6881908111cc47b5fe8b9e |
completed | May 2, 2026, 2:30 p.m. |
Created at: April 8, 2026, 9:50 p.m.