Triple
T15669901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Menkheperre |
E377279
|
entity |
| Predicate | belongsToNameType |
P1081
|
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: [Menkheperre, belongsToNameType, prenomen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNameType Context triple: [Menkheperre, belongsToNameType, prenomen]
-
A.
nameType
chosen
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
B.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
C.
onNameTypeLists
Indicates that something appears on one or more lists that are categorized or organized by name type.
-
D.
belongsToForceType
Indicates that an entity is associated with, or classified under, a specific type of force.
-
E.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1254508190a77a16b7bfd299ad |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.