Triple
T6707552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptah-Sokar-Osiris |
E153045
|
entity |
| Predicate | veneratedInContext |
P5315
|
FINISHED |
| Object | funerary cults |
—
|
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: funerary cults | Statement: [Ptah-Sokar-Osiris, veneratedInContext, funerary cults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedInContext Context triple: [Ptah-Sokar-Osiris, veneratedInContext, funerary cults]
-
A.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
B.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
D.
veneratedFigureMentioned
Indicates that a person who is highly respected or revered is explicitly referenced or mentioned in relation to another entity or context.
-
E.
venerationType
chosen
Indicates the specific manner or category of reverence or worship directed toward an entity.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.