Triple
T33585491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | usedOnTempleOf |
P177627
|
FINISHED |
| Object | Amun at Karnak (Senusret I constructions) |
—
|
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: Amun at Karnak (Senusret I constructions) | Statement: [Kheperkara, usedOnTempleOf, Amun at Karnak (Senusret I constructions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnTempleOf Context triple: [Kheperkara, usedOnTempleOf, Amun at Karnak (Senusret I constructions)]
-
A.
templeUse
Indicates that something is used as, functions as, or serves the purpose of a temple.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
residesInTemple
Indicates that one entity lives or dwells within a temple associated with another entity.
-
D.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
E.
elementRepresentedByMainTemple
Indicates that a particular element is symbolized or embodied by the main temple in a given religious or cultural context.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:40 a.m.