Triple
T32719372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobekkare |
E836625
|
entity |
| Predicate | usedForRegnalIdentificationOf |
P178278
|
FINISHED |
| Object | Sobekneferu |
—
|
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: Sobekneferu | Statement: [Sobekkare, usedForRegnalIdentificationOf, Sobekneferu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForRegnalIdentificationOf Context triple: [Sobekkare, usedForRegnalIdentificationOf, Sobekneferu]
-
A.
usedRegnalNumber
Indicates that an entity (such as a ruler or pope) bore or was designated by a specific regnal number as part of their official title.
-
B.
usedForRegnalYears
Indicates that something serves as the basis or reference system for counting and designating regnal years of a ruler.
-
C.
usedAsRoyalNameOn
chosen
Indicates that something served as a royal name or title during a specified time or in a specified context.
-
D.
namedForMonarch
Indicates that one entity bears a name derived from or given in honor of a monarch.
-
E.
tookRegnalName
Indicates that a person adopted and used a specific official regnal name upon assuming a throne or sovereign rulership.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:11 a.m.