Triple
T19726266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferneferuaten |
E473734
|
entity |
| Predicate | possiblySameAs |
P132057
|
FINISHED |
| Object | female ruler sometimes distinguished from Smenkhkare |
—
|
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: female ruler sometimes distinguished from Smenkhkare | Statement: [Neferneferuaten, possiblySameAs, female ruler sometimes distinguished from Smenkhkare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possiblySameAs Context triple: [Neferneferuaten, possiblySameAs, female ruler sometimes distinguished from Smenkhkare]
-
A.
possiblyIdenticalWith
chosen
Indicates that two entities may be the same individual or object, but this identity is uncertain or not definitively established.
-
B.
identifiedAsSameObjectAs
Indicates that two referenced entities are recognized or treated as being the very same underlying object or instance.
-
C.
sameMatchAs
Indicates that two entities are considered equivalent or represent the same underlying match or correspondence in a given context.
-
D.
samePersonAs
Indicates that two referenced entities are in fact the very same individual, not just similar or related.
-
E.
possiblyServedAs
Indicates that an entity may have held or fulfilled a particular role, position, or function, but this service is uncertain or not definitively confirmed.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f7bedc81908f784832c0fc10a1 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.