Triple
T30551171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poem of Pentaur |
E777562
|
entity |
| Predicate | placeOfInscription |
P31851
|
FINISHED |
| Object | Temple of Amun at Karnak |
—
|
NE NERFINISHED |
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: Temple of Amun at Karnak | Statement: [Poem of Pentaur, placeOfInscription, Temple of Amun at Karnak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfInscription Context triple: [Poem of Pentaur, placeOfInscription, Temple of Amun at Karnak]
-
A.
inscribedAt
Indicates that an entity is formally recorded, registered, or written onto a specific object, surface, or official list at a particular place or institution.
-
B.
inscriptionsFoundAt
chosen
Indicates that inscriptions are discovered or located at a particular place or site.
-
C.
unescoDesignation
Indicates that an entity has been granted a specific designation or status by UNESCO.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
heritageSiteLocation
Indicates that a heritage site is geographically located within or associated with a specific place or area.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 8:20 p.m.