Triple
T5992269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maat |
E133376
|
entity |
| Predicate | pharaohDuty |
P67880
|
FINISHED |
| Object | uphold Maat |
—
|
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: uphold Maat | Statement: [Maat, pharaohDuty, uphold Maat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pharaohDuty Context triple: [Maat, pharaohDuty, uphold Maat]
-
A.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
B.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
C.
pharaohOfBuilder
Indicates a relationship where a pharaoh is the ruler under whose authority or during whose reign a particular structure or monument was built.
-
D.
viewsPharaohAs
Indicates that one entity regards, interprets, or considers another entity specifically in the role or identity of a pharaoh.
-
E.
royalNecropolis
Indicates a burial place or cemetery specifically designated for royalty or members of a royal family.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e8fd030819095a4f3b3d425ec21 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04dbefd1081909795fe1a812b991a |
completed | March 22, 2026, 8:14 p.m. |
Created at: March 22, 2026, 4:05 p.m.