Triple
T18867491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maatkare |
E461477
|
entity |
| Predicate | royalProtocol |
P127798
|
FINISHED |
| Object | enclosed in a cartouche |
—
|
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: enclosed in a cartouche | Statement: [Maatkare, royalProtocol, enclosed in a cartouche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalProtocol Context triple: [Maatkare, royalProtocol, enclosed in a cartouche]
-
A.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
-
B.
royalVariant
Indicates a relationship where one entity is a special or modified version of another that is associated with royalty, nobility, or regal status.
-
C.
royalDuties
Indicates that an entity has responsibilities, obligations, or functions associated with a royal role or position.
-
D.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
-
E.
royalUse
chosen
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a6d1d081909b6dab2a5166a317 |
completed | April 20, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.