Triple
T29348180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV22 |
E744226
|
entity |
| Predicate | hasTombLayoutFeature |
P180791
|
FINISHED |
| Object | entrance corridor |
—
|
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: entrance corridor | Statement: [KV22, hasTombLayoutFeature, entrance corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTombLayoutFeature Context triple: [KV22, hasTombLayoutFeature, entrance corridor]
-
A.
hasTombChapel
Indicates that an entity possesses or is associated with a specific tomb chapel as part of its funerary or commemorative context.
-
B.
hasCemeteryFeature
Indicates that a cemetery possesses or is characterized by a specific feature or attribute.
-
C.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
D.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
E.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 28, 2026, 2:04 p.m.