Triple
T7316487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Djedefre |
E168424
|
entity |
| Predicate | hasNearbyMonuments |
P50236
|
FINISHED |
| Object | mastaba tombs of officials |
—
|
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: mastaba tombs of officials | Statement: [Pyramid of Djedefre, hasNearbyMonuments, mastaba tombs of officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMonuments Context triple: [Pyramid of Djedefre, hasNearbyMonuments, mastaba tombs of officials]
-
A.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
B.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
C.
hasNumberOfMonuments
Indicates the specific count of monuments associated with or present in a given entity.
-
D.
otherMonuments
chosen
Indicates that there exists a relationship between an entity and additional monuments that are associated with or related to it in some relevant way.
-
E.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef162d488190bf1c63b71b20a294 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.