Triple
T21685945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzbek culture |
E535227
|
entity |
| Predicate | associatedArchitecturalFeature |
P6684
|
FINISHED |
| Object | blue-tiled domes |
—
|
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: blue-tiled domes | Statement: [Uzbek culture, associatedArchitecturalFeature, blue-tiled domes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedArchitecturalFeature Context triple: [Uzbek culture, associatedArchitecturalFeature, blue-tiled domes]
-
A.
hasArchitecturalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
B.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
C.
architecturalUse
Indicates how a structure, space, or element is intended to be used or function within an architectural context.
-
D.
architectureAssociated
Indicates that there is a relationship or connection between an entity and a particular architectural style, feature, or practice.
-
E.
architecturalContribution
Indicates a relationship where an entity contributes to the design, planning, or creation of an architectural work or feature.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cb69f081908ed0c7ebea429898 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.