Triple
T12581510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amduat |
E300349
|
entity |
| Predicate | commonlyInscribedIn |
P105548
|
FINISHED |
| Object | royal tombs in the Valley of the Kings |
—
|
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: royal tombs in the Valley of the Kings | Statement: [Amduat, commonlyInscribedIn, royal tombs in the Valley of the Kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyInscribedIn Context triple: [Amduat, commonlyInscribedIn, royal tombs in the Valley of the Kings]
-
A.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
B.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
C.
inscribedTogetherWith
Indicates that one entity is inscribed jointly with another on the same surface, object, or document as part of a single inscription context.
-
D.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
E.
inscribedOn
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
- 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.