Triple
T15043672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses VI |
E379166
|
entity |
| Predicate | burialDiscovery |
P67779
|
FINISHED |
| Object | tomb KV9 known since antiquity |
—
|
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: tomb KV9 known since antiquity | Statement: [Ramesses VI, burialDiscovery, tomb KV9 known since antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialDiscovery Context triple: [Ramesses VI, burialDiscovery, tomb KV9 known since antiquity]
-
A.
tombDiscovered
chosen
Indicates that a tomb has been found or uncovered, typically as the result of exploration, excavation, or chance discovery.
-
B.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
E.
burialContext
Indicates the circumstances or setting in which a burial takes place, such as associated practices, location, or cultural conditions surrounding the interment.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82f73208190bb55fa6b20074e27 |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 3 a.m.