Triple
T37689544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspelta |
E938465
|
entity |
| Predicate | usedRoyalTitles |
P175311
|
FINISHED |
| Object | Egyptian pharaonic titulary |
—
|
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: Egyptian pharaonic titulary | Statement: [Aspelta, usedRoyalTitles, Egyptian pharaonic titulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRoyalTitles Context triple: [Aspelta, usedRoyalTitles, Egyptian pharaonic titulary]
-
A.
usesRoyalTitle
Indicates that one entity refers to another using a royal title or honorific (such as king, queen, prince, or similar).
-
B.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
-
C.
hasRoyalEpithets
chosen
Indicates that an entity is associated with one or more honorific or ceremonial titles traditionally used for royalty.
-
D.
royalTitularyFeature
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
E.
usedAsRoyalNameOn
Indicates that something served as a royal name or title during a specified time or in a specified context.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.