Triple
T26282148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perabsen |
E661026
|
entity |
| Predicate | didNotUseSerekhEmblem |
P160199
|
FINISHED |
| Object | Horus falcon |
—
|
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: Horus falcon | Statement: [Perabsen, didNotUseSerekhEmblem, Horus falcon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotUseSerekhEmblem Context triple: [Perabsen, didNotUseSerekhEmblem, Horus falcon]
-
A.
isAmongFirstToUseSerekh
Indicates that an entity is among the earliest known individuals or groups to employ a serekh (an early royal emblem) in association with their name or identity.
-
B.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
-
C.
hasSerekhName
Indicates that an entity (typically a ruler) possesses a specific serekh name, the early royal name written within a serekh frame.
-
D.
serekhContains
Indicates that a serekh symbol encloses or contains a specific element, such as a royal name or inscription.
-
E.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e74cdf08190b753c3c10691a440 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:01 p.m.