Triple
T34308510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Камен мост |
E880377
|
entity |
| Predicate | свързва |
P152948
|
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.
повʼязанеЗ
chosen
Indicates a general association or connection between one entity and another.
-
B.
συνδέεται_οδικά_με
Indicates that there is a road connection or roadway link between the two entities.
-
C.
associatedVow
Indicates a relationship where a vow is linked or connected to a particular entity or event.
-
D.
associatedWithSee
Indicates a relationship where one entity is contextually or functionally linked to another through the act or concept of seeing or visual observation.
-
E.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.