Triple
T34032305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Userkaf pyramid complex |
E872689
|
entity |
| Predicate | necropolis |
P76264
|
FINISHED |
| Object | Saqqara Necropolis |
—
|
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: Saqqara Necropolis | Statement: [Userkaf pyramid complex, necropolis, Saqqara Necropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: necropolis Context triple: [Userkaf pyramid complex, necropolis, Saqqara Necropolis]
-
A.
necropolisRole
Indicates that an entity has a specific functional or social role in relation to a necropolis (a large cemetery or burial ground).
-
B.
belongsToNecropolis
chosen
Indicates that something is part of, contained within, or associated with a particular necropolis.
-
C.
placeOfApotheosis
Indicates the location where a being undergoes or has undergone apotheosis, i.e., is elevated to divine or godlike status.
-
D.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
E.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.