Triple
T4243288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nekhbet |
E95465
|
entity |
| Predicate | worshipDuration |
P11027
|
FINISHED |
| Object | throughout most of ancient Egyptian history |
—
|
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: throughout most of ancient Egyptian history | Statement: [Nekhbet, worshipDuration, throughout most of ancient Egyptian history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipDuration Context triple: [Nekhbet, worshipDuration, throughout most of ancient Egyptian history]
-
A.
worshipPeriod
chosen
Indicates the time span or specific period during which an act of worship or religious devotion takes place.
-
B.
timePeriodOfWorship
Indicates the specific time period during which the worship activity takes place or is observed.
-
C.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
D.
worshipStyle
Indicates the manner or form in which worship or religious devotion is practiced or expressed.
-
E.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8a676c8190ac2cb59e62613dd9 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.