Triple
T21918227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian temples |
E541234
|
entity |
| Predicate | ritualsPerformed |
P70955
|
FINISHED |
| Object | daily cult of the god |
—
|
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: daily cult of the god | Statement: [Egyptian temples, ritualsPerformed, daily cult of the god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualsPerformed Context triple: [Egyptian temples, ritualsPerformed, daily cult of the god]
-
A.
ritualActivities
Indicates that one entity engages in, performs, or is associated with ritualistic or ceremonial activities in relation to another entity or context.
-
B.
hasRituals
chosen
Indicates that one entity performs, observes, or is associated with specific rituals in relation to another entity or context.
-
C.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
initiatesRitual
Indicates that one entity begins or sets in motion a ritual involving one or more other entities.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233924008190923724d0c0f2d435 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:43 p.m.