Triple
T31605516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villaz-Saint-Pierre |
E806472
|
entity |
| Predicate | sharesHealthcareSystemWith |
P186948
|
FINISHED |
| Object | Canton of Fribourg |
—
|
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: Canton of Fribourg | Statement: [Villaz-Saint-Pierre, sharesHealthcareSystemWith, Canton of Fribourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesHealthcareSystemWith Context triple: [Villaz-Saint-Pierre, sharesHealthcareSystemWith, Canton of Fribourg]
-
A.
shareHealthSystem
chosen
Indicates that two entities are served by, or belong to, the same healthcare system or network.
-
B.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
C.
sharesSystemWith
Indicates that two entities operate within or are associated with the same overarching system or environment.
-
D.
healthSystemLevel
Indicates the level or tier within a health system at which a given action, service, or relationship occurs (e.g., local, regional, national).
-
E.
sharesRitesWith
Indicates that two entities participate in or observe the same religious, ceremonial, or ritual practices.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 30, 2026, 10:34 p.m.