Triple
T27297600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ka-nakht-mery-Maat |
E688809
|
entity |
| Predicate | usedAsRoyalNameOn |
P178278
|
FINISHED |
| Object | monumental inscriptions |
—
|
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: monumental inscriptions | Statement: [Ka-nakht-mery-Maat, usedAsRoyalNameOn, monumental inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsRoyalNameOn Context triple: [Ka-nakht-mery-Maat, usedAsRoyalNameOn, monumental inscriptions]
-
A.
eraNameUsedDuringReign
Indicates that a particular era name was officially used throughout the duration of a ruler's reign.
-
B.
tookRegnalName
Indicates that a person adopted and used a specific official regnal name upon assuming a throne or sovereign rulership.
-
C.
usedForMonarchOf
Indicates that something serves as a means, tool, or context specifically for exercising the role or authority of a monarch.
-
D.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
E.
namedForMonarch
Indicates that one entity bears a name derived from or given in honor of a monarch.
- 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_69ef355a96308190a2bed991525fb278 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 27, 2026, 11:19 a.m.