Triple
T25598623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Kukulkan |
E641724
|
entity |
| Predicate | hasInnerStructure |
P134317
|
FINISHED |
| Object | earlier pyramid inside |
—
|
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: earlier pyramid inside | Statement: [Temple of Kukulkan, hasInnerStructure, earlier pyramid inside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInnerStructure Context triple: [Temple of Kukulkan, hasInnerStructure, earlier pyramid inside]
-
A.
hasOuterStructure
Indicates that one entity possesses or is characterized by an external or surrounding structural component formed by another entity.
-
B.
haveStructure
chosen
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
C.
hasHiddenStructure
Indicates that an entity possesses an internal or underlying structure that is not directly visible or apparent.
-
D.
hasMainStructure
Indicates that one entity serves as the primary or central structural component of another entity.
-
E.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 21, 2026, 4:29 p.m.