Triple
T19433371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenmesse |
E486169
|
entity |
| Predicate | royalPrenomenStatus |
P135869
|
FINISHED |
| Object | poorly attested |
—
|
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: poorly attested | Statement: [Amenmesse, royalPrenomenStatus, poorly attested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalPrenomenStatus Context triple: [Amenmesse, royalPrenomenStatus, poorly attested]
-
A.
royalPrenomen
Indicates the formal throne name adopted by a monarch as part of their royal titulary.
-
B.
royalNomen
Indicates that an entity bears a royal name or official titulary associated with monarchy or sovereign status.
-
C.
isPraenomenOf
Indicates that a given personal name functions as the praenomen (given name) of a specific individual.
-
D.
memberHasPraenomen
Indicates that a member is associated with or bears a specific praenomen (personal given name).
-
E.
praenomenStatus
Indicates the status or role associated with a person's praenomen (given name), such as whether it is official, alternative, uncertain, or otherwise qualified.
- F. None of above. chosen
Provenance (4 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.