Triple
T29272072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mersyankh III |
E742144
|
entity |
| Predicate | hasTombChapel |
P180627
|
FINISHED |
| Object | rock-cut chapel with painted reliefs |
—
|
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: rock-cut chapel with painted reliefs | Statement: [Mersyankh III, hasTombChapel, rock-cut chapel with painted reliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTombChapel Context triple: [Mersyankh III, hasTombChapel, rock-cut chapel with painted reliefs]
-
A.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
B.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
C.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 28, 2026, 12:48 p.m.