Triple
T34537417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hare nome |
E886706
|
entity |
| Predicate | hasCulticToponym |
P139594
|
FINISHED |
| Object | Khmunu (Hermopolis) |
—
|
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: Khmunu (Hermopolis) | Statement: [Hare nome, hasCulticToponym, Khmunu (Hermopolis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulticToponym Context triple: [Hare nome, hasCulticToponym, Khmunu (Hermopolis)]
-
A.
hasReligiousToponym
chosen
Indicates that a place name is derived from or explicitly references a religious figure, concept, institution, or tradition.
-
B.
hasCulticCenter
Indicates that an entity serves as the primary religious or ritual center associated with another entity.
-
C.
hasCulticInstallations
Indicates the presence of structures or features specifically designed or used for religious or ritual (cultic) practices.
-
D.
hasCultEpithetOfDeity
Indicates that a specific cult epithet or title is associated with, or used for, a particular deity.
-
E.
hasCultOrigin
Indicates that something originates from, or is derived from, a particular cult or cultic tradition.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 2:02 a.m.