Triple
T14898348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iunet |
E359936
|
entity |
| Predicate | hasCultCenterOf |
P36126
|
FINISHED |
| Object | Harsomtus |
E1054996
|
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: Harsomtus | Statement: [Iunet, hasCultCenterOf, Harsomtus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Harsomtus Context triple: [Iunet, hasCultCenterOf, Harsomtus]
-
A.
Harsomtus
chosen
Harsomtus is an Egyptian serpent or falcon-headed god associated with the sun’s daily rebirth and often linked to child deities like Ihy in local cults.
-
B.
Clytoneus
Clytoneus is a minor figure in Greek mythology, known as one of the sons of King Alcinous of the Phaeacians in Homer’s Odyssey.
-
C.
Calophysus
Calophysus is a genus of South American freshwater catfish known for its scavenging habits and occurrence in large river systems such as the Amazon.
-
D.
Taphius
Taphius is a minor figure in Greek mythology known as a son of the sea god Poseidon.
-
E.
Ambrysus
Ambrysus was an ancient Greek city in the region of Phocis, known for its strategic location and role in classical Greek history.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6084574819098033a9723f3e1c4 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe6b6966e88190a0ed475b22a77cf1 |
completed | May 8, 2026, 11:02 p.m. |
Created at: April 10, 2026, 2:11 a.m.