Triple
T5860092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Teti |
E130253
|
entity |
| Predicate | hasNearbyBurials |
P42242
|
FINISHED |
| Object | mastabas of officials of Teti’s reign |
—
|
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: mastabas of officials of Teti’s reign | Statement: [Pyramid of Teti, hasNearbyBurials, mastabas of officials of Teti’s reign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyBurials Context triple: [Pyramid of Teti, hasNearbyBurials, mastabas of officials of Teti’s reign]
-
A.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
B.
hasNearbyCemetery
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another entity.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
E.
numberOfBurials
Indicates the total count of burial events associated with a given 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.