Triple
T16630522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merenkahre |
E404065
|
entity |
| Predicate | fictionalCulture |
P59975
|
FINISHED |
| Object | ancient Egyptian |
—
|
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: ancient Egyptian | Statement: [Merenkahre, fictionalCulture, ancient Egyptian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalCulture Context triple: [Merenkahre, fictionalCulture, ancient Egyptian]
-
A.
cultureInFiction
Indicates that a work of fiction features, represents, or is thematically centered on a particular culture.
-
B.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
C.
fictionalEthnoCulturalIdentity
chosen
Indicates that an entity is associated with an invented or imaginary ethnic or cultural identity, rather than a real-world one.
-
D.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
E.
fictionalMedium
Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e5d4448190bfb1b6157bbe5285 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.