Triple
T34628892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Khufu |
E889216
|
entity |
| Predicate | religionOfContext |
P9028
|
FINISHED |
| Object | Ancient Egyptian religion |
—
|
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: Ancient Egyptian religion | Statement: [House of Khufu, religionOfContext, Ancient Egyptian religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionOfContext Context triple: [House of Khufu, religionOfContext, Ancient Egyptian religion]
-
A.
originReligionContext
Indicates the religious background or setting from which something or someone originates or is derived.
-
B.
typicalReligionContext
Indicates the usual or most common religious setting, tradition, or affiliation associated with an entity or situation.
-
C.
religiousCulturalContext
chosen
Indicates the religious or cultural setting, tradition, or framework within which an entity, practice, or event occurs or is interpreted.
-
D.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
E.
religionOrWorldviewContext
Indicates the religious or worldview setting within which an action, belief, or relationship takes place or is interpreted.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 1, 2026, 2:04 a.m.