Triple
T20533126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Userkaf |
E504119
|
entity |
| Predicate | throneName |
P25582
|
FINISHED |
| Object | Userkaf |
—
|
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: Userkaf | Statement: [Userkaf, throneName, Userkaf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Userkaf Context triple: [Userkaf, throneName, Userkaf]
-
A.
Userkaf
chosen
Userkaf was a pharaoh of Egypt’s Fifth Dynasty, best known for initiating the construction of sun temples and helping establish the prominence of the solar cult of Ra.
-
B.
Userkare
Userkare was a short-reigning pharaoh of Egypt’s Sixth Dynasty, known primarily from sparse archaeological and textual evidence that leaves many details of his rule uncertain.
-
C.
Userin
Userin is a small settlement in the Mecklenburgische Seenplatte region of Mecklenburg-Vorpommern in northeastern Germany.
-
D.
Usery
Usery is a surname most notably associated with William J. Usery Jr., a prominent American labor union activist and U.S. Secretary of Labor.
-
E.
Meuser
Meuser is a German-language surname borne by various individuals, including American politician Dan Meuser.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06d30508190a13d1a9855b441fb |
completed | April 20, 2026, 9:53 p.m. |
Created at: April 16, 2026, 11:37 a.m.