Triple
T24673196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Ramesses VI |
E610901
|
entity |
| Predicate | laterAppropriatedBy |
P123303
|
FINISHED |
| Object | Ramesses VI |
—
|
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: Ramesses VI | Statement: [Tomb of Ramesses VI, laterAppropriatedBy, Ramesses VI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAppropriatedBy Context triple: [Tomb of Ramesses VI, laterAppropriatedBy, Ramesses VI]
-
A.
laterUsurpedBy
chosen
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
-
B.
laterAdoptedBy
Indicates that one entity is adopted by another entity at a later point in time, after some prior state or relationship has already been established.
-
C.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
D.
laterUsedBy
Indicates that something is subsequently utilized or employed by a specified entity at a later time.
-
E.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:48 a.m.