Triple
T19726188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebkheperure |
E473733
|
entity |
| Predicate | titularyType |
P6489
|
FINISHED |
| Object | prenomen |
—
|
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: prenomen | Statement: [Nebkheperure, titularyType, prenomen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titularyType Context triple: [Nebkheperure, titularyType, prenomen]
-
A.
titularyPosition
Indicates that one entity holds a formal or ceremonial title or position in relation to another entity.
-
B.
titleType
chosen
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
-
C.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
D.
isTitularChurchTitleOf
Indicates that a given church serves as the official titular church associated with a particular cardinal’s title.
-
E.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary title.
- 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.