Triple
T12581529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amduat |
E300349
|
entity |
| Predicate | typicalLocationInTomb |
P105549
|
FINISHED |
| Object | corridors and burial chambers |
—
|
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: corridors and burial chambers | Statement: [Amduat, typicalLocationInTomb, corridors and burial chambers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationInTomb Context triple: [Amduat, typicalLocationInTomb, corridors and burial chambers]
-
A.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
B.
tombLocatedAtSite
Indicates that a tomb is situated at, or physically located within, a particular archaeological or geographic site.
-
C.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
D.
coffinLocation
Indicates the place where a coffin is situated or stored.
-
E.
mortuaryTempleLocation
Indicates that a mortuary temple is located at or associated with a specific place or site.
- F. None of above. chosen
Provenance (4 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d954e351f88190869220d46e0ce282 |
completed | April 10, 2026, 7:52 p.m. |
Created at: April 9, 2026, 5:02 p.m.