Triple
T27843613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | имаАрхитектонскиЕлементи |
P86921
|
FINISHED |
| Object | колонади |
—
|
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: колонади | Statement: [Плоштад Македонија, имаАрхитектонскиЕлементи, колонади]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имаАрхитектонскиЕлементи Context triple: [Плоштад Македонија, имаАрхитектонскиЕлементи, колонади]
-
A.
architecturalWork
Indicates that one entity is an architectural creation (such as a building or structure) designed or realized by another entity.
-
B.
architecturalSymbol
Indicates that one entity serves as a symbolic or emblematic representation of another within an architectural context.
-
C.
architecturalConcept
Indicates that one entity represents or embodies an architectural concept in relation to another entity.
-
D.
mainArchitecturalForm
Indicates the primary architectural style or structural form that characterizes a building or construction.
-
E.
typicalStructuralElement
chosen
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part of 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f638d838c481909fbe470bb85c30b1 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:05 p.m.