Triple
T27297610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ka-nakht-mery-Maat |
E688809
|
entity |
| Predicate | usedByPosition |
P173358
|
FINISHED |
| Object | last native pharaoh of Egypt |
—
|
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: last native pharaoh of Egypt | Statement: [Ka-nakht-mery-Maat, usedByPosition, last native pharaoh of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByPosition Context triple: [Ka-nakht-mery-Maat, usedByPosition, last native pharaoh of Egypt]
-
A.
usedByPositionHolder
Indicates that something (such as a resource, tool, or asset) is utilized by the person or role currently holding a specific position.
-
B.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
C.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given context.
-
D.
usedByLine
Indicates that something (such as a resource, tool, or component) is utilized or operated by a particular line (for example, a production line, transit line, or code line).
-
E.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
- 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_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 27, 2026, 11:19 a.m.