Triple
T27169393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takelot III |
E682862
|
entity |
| Predicate | hasRoyalEpithets |
P175311
|
FINISHED |
| Object | Beloved of Amun |
—
|
NE NERFINISHED |
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: Beloved of Amun | Statement: [Takelot III, hasRoyalEpithets, Beloved of Amun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalEpithets Context triple: [Takelot III, hasRoyalEpithets, Beloved of Amun]
-
A.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
D.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
E.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 27, 2026, 9:22 a.m.