Triple
T32230816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebhepetre |
E823335
|
entity |
| Predicate | usedInRoyalInscriptions |
P156954
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nebhepetre, usedInRoyalInscriptions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRoyalInscriptions Context triple: [Nebhepetre, usedInRoyalInscriptions, yes]
-
A.
usedInOfficialInscriptions
Indicates that something is employed or appears in formal, sanctioned, or authoritative inscriptions or records.
-
B.
attestedInInscriptions
chosen
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
-
C.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
-
D.
hasInscriptionFromReignOf
Indicates that an object bears an inscription created during the reign of a specified ruler or authority.
-
E.
usedAsRoyalNameOn
Indicates that something served as a royal name or title during a specified time or in a specified context.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 1, 2026, 12:39 a.m.