Triple
T27843621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Плоштад Македонија |
E703754
|
entity |
| Predicate | еДелОд |
P163407
|
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.
subjectOfDecreeBy
Indicates that an entity is the topic or matter formally addressed, regulated, or decided upon in an official decree issued by another entity.
-
B.
deed
Indicates that an entity performs, carries out, or is responsible for a particular action or act.
-
C.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
-
D.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
E.
officeInvolved
Indicates that a particular office or organizational unit is involved or participates in a specified event, action, or relationship.
- 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.