Triple
T33409273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ameny Qemau |
E855528
|
entity |
| Predicate | pyramidAttributionMethod |
P176562
|
FINISHED |
| Object | inscriptions bearing his name |
—
|
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: inscriptions bearing his name | Statement: [Ameny Qemau, pyramidAttributionMethod, inscriptions bearing his name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pyramidAttributionMethod Context triple: [Ameny Qemau, pyramidAttributionMethod, inscriptions bearing his name]
-
A.
pyramidAttributionStatus
Indicates the current status or state of attribution assigned to a given pyramid.
-
B.
pyramidDesignAttribution
Indicates that the design of a pyramid is attributed to a particular agent, such as an architect, builder, or cultural group.
-
C.
pyramidAlternativeName
Indicates that a pyramid is known or referred to by an alternative name or alias.
-
D.
pyramidAssociatedStructure
Indicates a structural or architectural feature that is functionally or historically connected to a pyramid.
-
E.
pyramidName
Indicates that a pyramid is associated with a specific name or title.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.