Triple
T29347936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nebmaatre |
E744220
|
entity |
| Predicate | usedInRoyalTitulary |
P78578
|
FINISHED |
| Object | prenomen cartouche |
—
|
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 cartouche | Statement: [Nebmaatre, usedInRoyalTitulary, prenomen cartouche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRoyalTitulary Context triple: [Nebmaatre, usedInRoyalTitulary, prenomen cartouche]
-
A.
usedAsRoyalNameOn
Indicates that something served as a royal name or title during a specified time or in a specified context.
-
B.
usedInMonarchy
Indicates that something is employed, practiced, or functions within the context of a monarchical system of government.
-
C.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
D.
usedRoyalTitlesOf
Indicates that one entity employed or adopted the royal titles belonging to or associated with another entity.
-
E.
usedForMonarchOf
Indicates that something serves as a means, tool, or context specifically for exercising the role or authority of a monarch.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 28, 2026, 2:03 p.m.