Triple
T33409287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ameny Qemau |
E855528
|
entity |
| Predicate | hasCartouche |
P36811
|
FINISHED |
| Object | cartouche with the name Ameny Qemau |
—
|
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: cartouche with the name Ameny Qemau | Statement: [Ameny Qemau, hasCartouche, cartouche with the name Ameny Qemau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCartouche Context triple: [Ameny Qemau, hasCartouche, cartouche with the name Ameny Qemau]
-
A.
usedAsCartoucheName
Indicates that a given name or designation is employed as the text enclosed within a cartouche.
-
B.
writtenWithCartouche
Indicates that the text or name is inscribed enclosed within a cartouche.
-
C.
featuresCartouchesOf
chosen
Indicates that something (such as an artifact, monument, or object) bears or includes cartouches that contain the names or titles of specific individuals or entities.
-
D.
hasCarving
Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
-
E.
hasCartridgeSlot
Indicates that an object includes a dedicated slot or receptacle designed to accept and hold a cartridge.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 1:36 a.m.