Triple
T34377486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferu III |
E882327
|
entity |
| Predicate | burialComplexOf |
P179142
|
FINISHED |
| Object | Senusret I pyramid complex at Lisht |
—
|
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: Senusret I pyramid complex at Lisht | Statement: [Neferu III, burialComplexOf, Senusret I pyramid complex at Lisht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialComplexOf Context triple: [Neferu III, burialComplexOf, Senusret I pyramid complex at Lisht]
-
A.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
B.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
-
C.
partOfDynasticComplex
Indicates that one entity is a constituent element or subdivision within a larger dynastic complex or ruling lineage structure.
-
D.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
E.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
- F. None of above. chosen
Provenance (4 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71c33edac8190a59f6ff19b265fc5 |
completed | May 3, 2026, 9:58 a.m. |
Created at: May 1, 2026, 1:59 a.m.