Triple
T15337240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Kha and Merit |
E366697
|
entity |
| Predicate | hasOccupantStatus |
P118169
|
FINISHED |
| Object | non-royal elite |
—
|
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: non-royal elite | Statement: [Tomb of Kha and Merit, hasOccupantStatus, non-royal elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccupantStatus Context triple: [Tomb of Kha and Merit, hasOccupantStatus, non-royal elite]
-
A.
hasOccupancyStatus
Indicates the current usage or availability state of something, such as whether it is occupied, vacant, or otherwise in use.
-
B.
hasReservationStatus
Indicates that an entity is associated with a specific reservation and the current status or state of that reservation (e.g., pending, confirmed, canceled).
-
C.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
D.
occupiedBy
Indicates that a space, position, or role is currently being used, held, or filled by a particular entity.
-
E.
hasPrimaryOccupants
Indicates that certain entities are the main or principal occupants of another entity (such as a space, structure, or location).
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e11b22c81908280efe65acd5454 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:17 a.m.