Triple
T30298025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramesses XI |
E770572
|
entity |
| Predicate | tombAttributed |
P72397
|
FINISHED |
| Object | KV4 |
—
|
NE NERFINISHED |
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: KV4 | Statement: [Ramesses XI, tombAttributed, KV4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tombAttributed Context triple: [Ramesses XI, tombAttributed, KV4]
-
A.
associatedTomb
chosen
Indicates a relationship in which an entity is linked to or connected with a particular tomb, such as by burial, ownership, dedication, or commemoration.
-
B.
tombOwnership
Indicates a relationship in which one entity holds legal or traditional ownership rights over a specific tomb.
-
C.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
D.
tombExtendedBy
Indicates that a tomb has been enlarged, lengthened, or otherwise physically extended by another structure, addition, or modification.
-
E.
tombCategory
Indicates the classification or type of a tomb that an entity is associated with.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f681386a748190b0d383b7c580ab47 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:48 p.m.