Triple
T27843619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | имаФункција |
P81043
|
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.
functie
chosen
Indicates that one entity serves as a function, role, or operational purpose in relation to another entity.
-
B.
језикФункције
Indicates that something is the programming or implementation language used for a given function.
-
C.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
D.
usesFunction
Indicates that one entity employs, invokes, or relies on a particular function to perform an operation or achieve a result.
-
E.
junctionFunction
Indicates a functional relationship where one entity serves as a junction or connection point integrating or routing flows, signals, or interactions between multiple other entities.
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:05 p.m.