Triple
T25544947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramids of the Fifth Dynasty of Egypt |
E640272
|
entity |
| Predicate | mainCemeteryArea |
P154210
|
FINISHED |
| Object | Abusir 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: Abusir necropolis | Statement: [Pyramids of the Fifth Dynasty of Egypt, mainCemeteryArea, Abusir necropolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCemeteryArea Context triple: [Pyramids of the Fifth Dynasty of Egypt, mainCemeteryArea, Abusir necropolis]
-
A.
cemeteryArea
Indicates that an area or region is designated, used, or recognized as a cemetery.
-
B.
usedAsMainCemeteryOf
chosen
Indicates that one location functions as the primary burial ground or principal cemetery serving another entity (such as a settlement, community, or institution).
-
C.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
D.
cemeteryComplex
Indicates a relationship where a site or structure functions as, or is part of, a cemetery complex used for burials or memorials.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 3:28 p.m.