Triple
T2794226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepi I Meryre |
E52997
|
entity |
| Predicate | pyramidTextInscriptions |
P43186
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pepi I Meryre, pyramidTextInscriptions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pyramidTextInscriptions Context triple: [Pepi I Meryre, pyramidTextInscriptions, yes]
-
A.
scriptOfInscription
Indicates the writing system or script in which a given inscription is written.
-
B.
mainContentOfInscriptions
Indicates that something represents the primary textual or symbolic content conveyed by a set of inscriptions.
-
C.
lastKnownHieroglyphicInscriptionSite
Indicates the location where the most recent or final known hieroglyphic inscription associated with an entity was created or recorded.
-
D.
inscriptionsFoundAt
Indicates that inscriptions are discovered or located at a particular place or site.
-
E.
nameInHieroglyphs
Indicates that an entity’s name is written or represented using hieroglyphic script.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddd48bcc819083f4ec59d66f0ece |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddcc348081908b5f760899389d4f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 9:58 p.m.