Triple
T26588054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shabaka Stone inscription |
E667262
|
entity |
| Predicate | inscribedForRuler |
P42657
|
FINISHED |
| Object | Shabaka |
—
|
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: Shabaka | Statement: [Shabaka Stone inscription, inscribedForRuler, Shabaka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscribedForRuler Context triple: [Shabaka Stone inscription, inscribedForRuler, Shabaka]
-
A.
inscribedFor
chosen
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
B.
hasInscriptionFromReignOf
Indicates that an object bears an inscription created during the reign of a specified ruler or authority.
-
C.
signedByRuler
Indicates that an official document, decree, or agreement has been formally endorsed and authenticated through the signature of a ruling authority.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
inscribedUnder
Indicates that one entity is written, carved, or engraved beneath another entity, typically as a subordinate or accompanying inscription.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:06 a.m.