Triple
T3546233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahun Pyramid |
E75002
|
entity |
| Predicate | hasSubstructureType |
P841
|
FINISHED |
| Object | labyrinthine corridor system |
—
|
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: labyrinthine corridor system | Statement: [Lahun Pyramid, hasSubstructureType, labyrinthine corridor system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubstructureType Context triple: [Lahun Pyramid, hasSubstructureType, labyrinthine corridor system]
-
A.
containsAsSubstructure
Indicates that one structure includes another structure entirely within it as a component or embedded part.
-
B.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
D.
hasSubOrganizationType
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
E.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
- 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.