Triple
T33633027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Amenemhat |
E861616
|
entity |
| Predicate | usedRoyalIconography |
P162686
|
FINISHED |
| Object | Middle Kingdom style |
—
|
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: Middle Kingdom style | Statement: [House of Amenemhat, usedRoyalIconography, Middle Kingdom style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRoyalIconography Context triple: [House of Amenemhat, usedRoyalIconography, Middle Kingdom style]
-
A.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
B.
hasRoyalSymbol
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
C.
usedAsRoyalFavor
Indicates that something is employed or granted as a token of royal favor, privilege, or goodwill from a monarch or ruling authority.
-
D.
usesImperialRegalia
Indicates that one entity employs or incorporates imperial regalia (such as crowns, scepters, or other sovereign insignia) in relation to another entity or context.
-
E.
emblemUsedIn
chosen
Indicates that a particular emblem is utilized or displayed within a specific context, setting, 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:41 a.m.