Triple
T33766399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid at el-Lisht |
E865240
|
entity |
| Predicate | casingStonesReusedIn |
P82152
|
FINISHED |
| Object | later constructions in Cairo region |
—
|
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: later constructions in Cairo region | Statement: [Pyramid at el-Lisht, casingStonesReusedIn, later constructions in Cairo region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: casingStonesReusedIn Context triple: [Pyramid at el-Lisht, casingStonesReusedIn, later constructions in Cairo region]
-
A.
casingStonesPresent
Indicates that the outer protective or decorative casing stones are present on a structure or object.
-
B.
rebuiltInStone
Indicates that a previously existing structure was reconstructed using stone as the primary building material.
-
C.
usesOriginalStones
chosen
Indicates that something is constructed or preserved using the same stones that were part of the original structure or artifact.
-
D.
numberOfMajorStones
Indicates the quantity of major stones associated with or involved in a given entity or context.
-
E.
materialFromQuarriesUsedFor
Indicates that material extracted from quarries is used for a particular purpose, project, or object.
- 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.