Triple
T34353538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merneferre Ay |
E881649
|
entity |
| Predicate | royalHorusNameUnknown |
P122140
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Merneferre Ay, royalHorusNameUnknown, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHorusNameUnknown Context triple: [Merneferre Ay, royalHorusNameUnknown, true]
-
A.
usedHorusName
Indicates that one entity employed or was identified by the Horus name associated with another entity.
-
B.
ancientNameUnknown
chosen
Indicates that the ancient or original name associated with an entity is not known or cannot be determined.
-
C.
usedRoyalSerekh
Indicates that one entity employed or displayed the royal serekh (a pharaonic name emblem) associated with another entity.
-
D.
hasSerekhName
Indicates that an entity (typically a ruler) possesses a specific serekh name, the early royal name written within a serekh frame.
-
E.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
- 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_69f349bd06008190904c2f86c42749e3 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.