Triple
T27843632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | имаОколниОбјекти |
P163409
|
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.
relatedAstronomicalObject
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
-
B.
orbitsNear
Indicates that one object travels around another along a path that remains relatively close in spatial proximity.
-
C.
nearbyObjectOnSky
Indicates that one object appears close to another object in the sky, as observed from a given viewpoint.
-
D.
nearbyBody
Indicates that one physical body is located close in space to another body, within a defined proximity threshold.
-
E.
hasNearbyObservatories
Indicates that one entity has one or more observatories located in close geographic proximity to it.
- 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_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. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 6:05 p.m.