Triple
T32243080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kosovo |
E823669
|
entity |
| Predicate | hasHealthSystemLinkedTo |
P192927
|
FINISHED |
| Object | Serbia |
—
|
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: Serbia | Statement: [Northern Kosovo, hasHealthSystemLinkedTo, Serbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthSystemLinkedTo Context triple: [Northern Kosovo, hasHealthSystemLinkedTo, Serbia]
-
A.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
B.
hasOwnHealthSystem
Indicates that an entity operates and controls its own dedicated healthcare system, rather than relying solely on external or shared health services.
-
C.
hasHealthCareCharacteristic
Indicates that an entity possesses a specific healthcare-related attribute, quality, or feature.
-
D.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
E.
hasHealthCareInstitutionType
Indicates that an entity is classified as a specific type or category of healthcare institution.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: May 1, 2026, 12:40 a.m.