Triple
T32790113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khakhaure |
E838602
|
entity |
| Predicate | linkedToBurialSite |
P94045
|
FINISHED |
| Object | Giza pyramid complex |
—
|
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: Giza pyramid complex | Statement: [Khakhaure, linkedToBurialSite, Giza pyramid complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToBurialSite Context triple: [Khakhaure, linkedToBurialSite, Giza pyramid complex]
-
A.
burialSiteNear
Indicates that the burial site of one entity is located geographically close to another entity.
-
B.
belongsToNecropolis
Indicates that something is part of, contained within, or associated with a particular necropolis.
-
C.
associatedCemetery
chosen
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
D.
associatedTomb
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
E.
buriedNear
Indicates that one entity is interred or buried in close physical proximity 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 1, 2026, 1:14 a.m.