Triple
T34871371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec architecture |
E1005759
|
entity |
| Predicate | secularStructureType |
P115489
|
FINISHED |
| Object | palace complex |
—
|
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: palace complex | Statement: [Aztec architecture, secularStructureType, palace complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secularStructureType Context triple: [Aztec architecture, secularStructureType, palace complex]
-
A.
hasSecularStatus
chosen
Indicates that an entity holds a non-religious, secular standing or classification within a given context.
-
B.
ecclesiasticalType
Indicates the specific ecclesiastical category or classification that applies to a religious entity within a church hierarchy.
-
C.
superstructureType
Indicates the specific kind or design category of a structure’s superstructure that an entity possesses or is associated with.
-
D.
laterStructureType
Indicates that one structure is of a type that occurs or is instantiated later than another structure in a temporal or sequential sense.
-
E.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.