Triple
T19120179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wepwawet |
E468019
|
entity |
| Predicate | hasCultRole |
P81935
|
FINISHED |
| Object | guardian of necropoleis |
—
|
LITERAL 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: guardian of necropoleis | Statement: [Wepwawet, hasCultRole, guardian of necropoleis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultRole Context triple: [Wepwawet, hasCultRole, guardian of necropoleis]
-
A.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasCultLeaderCharacter
Indicates that an entity includes or features a character who acts as a cult leader, exerting charismatic, manipulative, and controlling influence over a group.
-
C.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
D.
hasCultFeature
chosen
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
-
E.
hasCulturalRole
Indicates that an entity fulfills or is assigned a specific function, position, or significance within a cultural, social, or traditional context.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3c810808190a88d5c7859e7c650 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.