Triple
T27890651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAR Museum |
E705344
|
entity |
| Predicate | hasArchitecturalStyleContext |
P607
|
FINISHED |
| Object | Georgian |
—
|
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: Georgian | Statement: [DAR Museum, hasArchitecturalStyleContext, Georgian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecturalStyleContext Context triple: [DAR Museum, hasArchitecturalStyleContext, Georgian]
-
A.
architecturalStyleIncludes
Indicates that a structure, building, or design incorporates or exemplifies a particular architectural style as one of its defining characteristics.
-
B.
architecturalStyle
chosen
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
-
C.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
D.
hasArchitecturalContextNearby
Indicates that one entity is situated close to another entity that provides relevant architectural context or surroundings.
-
E.
hasArchitecturalTheme
Indicates that one entity features or embodies a particular architectural style, motif, or design concept associated with another 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 6:35 p.m.