Triple
T26736001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skopje Region |
E674109
|
entity |
| Predicate | containsPresidentialResidence |
P30677
|
FINISHED |
| Object | Villa Vodno |
—
|
NE NERFINISHED |
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: Villa Vodno | Statement: [Skopje Region, containsPresidentialResidence, Villa Vodno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPresidentialResidence Context triple: [Skopje Region, containsPresidentialResidence, Villa Vodno]
-
A.
formerOfficialResidence
Indicates that a location previously served as the official residence of a person or institution but no longer holds that status.
-
B.
formerCapitalResidence
Indicates that an entity once served as the official residence associated with a capital (such as a capital city or seat of government) but no longer holds that status.
-
C.
containsPresidentialPalace
chosen
Indicates that a location or area includes within its boundaries a building that serves as a presidential palace.
-
D.
otherOfficialResidence
Indicates that an entity has an additional, secondary official residence distinct from its primary official residence.
-
E.
homeOfPresident
Indicates the location that serves as the residence of a president.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 3:47 a.m.