Triple
T23269151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deir el-Hagar |
E588240
|
entity |
| Predicate | hasInscriptionsOf |
P16756
|
FINISHED |
| Object | Roman emperors |
—
|
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: Roman emperors | Statement: [Deir el-Hagar, hasInscriptionsOf, Roman emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInscriptionsOf Context triple: [Deir el-Hagar, hasInscriptionsOf, Roman emperors]
-
A.
hasInscriptions
chosen
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
B.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
C.
numberOfInscriptions
Indicates the total count of inscriptions associated with a given entity or object.
-
D.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
-
E.
commonlyInscribedIn
Indicates that something is typically written, carved, or engraved onto a particular surface, object, or medium.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:45 p.m.