Triple
T27169445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudamun |
E682863
|
entity |
| Predicate | royalSymbol |
P115726
|
FINISHED |
| Object | double crown 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: double crown of Egypt | Statement: [Rudamun, royalSymbol, double crown of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalSymbol Context triple: [Rudamun, royalSymbol, double crown of Egypt]
-
A.
royalStandard
Indicates that an entity is the official royal flag or emblem used to represent a monarch or royal authority.
-
B.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
C.
dynasticSymbolOf
chosen
Indicates a symbolic association where something serves as an emblem or heraldic sign representing a particular dynasty.
-
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.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62545e210819090004d7c65f4898d |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:22 a.m.