Triple
T11039266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemkhet |
E260964
|
entity |
| Predicate | pyramidComplexFeature |
P37172
|
FINISHED |
| Object | enclosure wall |
—
|
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: enclosure wall | Statement: [Sekhemkhet, pyramidComplexFeature, enclosure wall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pyramidComplexFeature Context triple: [Sekhemkhet, pyramidComplexFeature, enclosure wall]
-
A.
hasPyramidComplexAt
Indicates that an entity possesses or is associated with a pyramid complex located at a specified place.
-
B.
pyramidFunction
Indicates a functional or hierarchical relationship where one entity operates at the apex or controlling level over multiple subordinate entities, analogous to a pyramid structure.
-
C.
pyramidAssociatedStructure
chosen
Indicates a structural or architectural feature that is functionally or historically connected to a pyramid.
-
D.
PoissonComparison
Indicates a relationship where two quantities or processes are compared under a Poisson-based statistical model, typically to assess whether their event rates differ significantly.
-
E.
pyramidShape
Indicates that an entity has the geometric form or overall structure of a pyramid.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fe93b081909d58bfd4b42715f0 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.