Triple
T3546237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahun Pyramid |
E75002
|
entity |
| Predicate | hasAssociatedTemple |
P13905
|
FINISHED |
| Object | mortuary temple on east side |
—
|
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: mortuary temple on east side | Statement: [Lahun Pyramid, hasAssociatedTemple, mortuary temple on east side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedTemple Context triple: [Lahun Pyramid, hasAssociatedTemple, mortuary temple on east side]
-
A.
associatedTemple
chosen
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
associatedWithTempleTown
Indicates a relationship where an entity has a connection or linkage to a town that is characterized by or centered around a temple.
-
C.
hasSubTemple
Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
-
D.
hasHistoricTemple
Indicates that an entity possesses, contains, or is associated with a temple of historical significance.
-
E.
hasTempleCount
Indicates that an entity is associated with a specified number of temples.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.