Triple
T1276148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptians |
E27216
|
entity |
| Predicate | ancientReligionHistorical |
P7641
|
FINISHED |
| Object | Ancient Egyptian religion |
—
|
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: Ancient Egyptian religion | Statement: [Egyptians, ancientReligionHistorical, Ancient Egyptian religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancientReligionHistorical Context triple: [Egyptians, ancientReligionHistorical, Ancient Egyptian religion]
-
A.
religionHistoricallyAssociated
chosen
Indicates a historical association between an entity and a particular religion, based on past practice, tradition, or cultural linkage rather than current or official status.
-
B.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
-
C.
dynasticReligion
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
D.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
E.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.