Triple
T27843635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | еПопуларноМестоЗа |
P3033
|
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.
regionPopularFor
Indicates that a particular region is well known or widely recognized for a specific activity, product, feature, or characteristic.
-
B.
popularTown
Indicates that a town is widely liked, frequently visited, or well-regarded by many people.
-
C.
popularFor
chosen
Indicates that something is widely liked, recognized, or favored specifically because of a particular feature, quality, or use.
-
D.
isPopularTouristDestinationIn
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
-
E.
promotionPlaces
Indicates that one entity designates or assigns another entity to a higher position, rank, or status within some organizational or hierarchical structure.
- 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.