Triple
T6932374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid B at Tula |
E160465
|
entity |
| Predicate | superstructureType |
P73759
|
FINISHED |
| Object | temple with columns on summit |
—
|
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: temple with columns on summit | Statement: [Pyramid B at Tula, superstructureType, temple with columns on summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superstructureType Context triple: [Pyramid B at Tula, superstructureType, temple with columns on summit]
-
A.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
B.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
towerType
Indicates the specific kind or classification of a tower that an entity is associated with or represents.
-
D.
typeOfTransportInfrastructure
Indicates the specific category or kind of transport infrastructure associated with or used in a given context.
-
E.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
- F. None of above. chosen
Provenance (4 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da3fa7fc8190a03e7132871a9af4 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:27 p.m.