Triple
T30354250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huny |
E772101
|
entity |
| Predicate | hasPossibleBurialSite |
P86191
|
FINISHED |
| Object | Meidum pyramid (disputed) |
—
|
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: Meidum pyramid (disputed) | Statement: [Huny, hasPossibleBurialSite, Meidum pyramid (disputed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPossibleBurialSite Context triple: [Huny, hasPossibleBurialSite, Meidum pyramid (disputed)]
-
A.
hasUncertainBurialSite
chosen
Indicates that the location of an entity’s burial site is unknown, disputed, or not reliably established.
-
B.
hasBuriedRemains
Indicates that one entity contains or is the location of the buried remains of another entity.
-
C.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
D.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 7:56 p.m.