Triple
T29348168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV22 |
E744226
|
entity |
| Predicate | chronologicalPositionInValley |
P10630
|
FINISHED |
| Object | early 18th Dynasty tomb |
—
|
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: early 18th Dynasty tomb | Statement: [KV22, chronologicalPositionInValley, early 18th Dynasty tomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPositionInValley Context triple: [KV22, chronologicalPositionInValley, early 18th Dynasty tomb]
-
A.
chronologicalPosition
chosen
Indicates the relative ordering of one event or entity in time with respect to another.
-
B.
isInValley
Indicates that an entity is located within or occupies the area of a valley.
-
C.
chronologicalPositionInLabors
Indicates the specific order or sequence in which a given labor occurs within a defined series of labors.
-
D.
chronologicalPositionInEpicCycle
Indicates the relative order or placement of an event, episode, or work within the overall sequence of an epic cycle.
-
E.
hasValley
Indicates that one entity contains, features, or is characterized by the presence of a valley associated with the other 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 2:04 p.m.