Triple
T31605515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villaz-Saint-Pierre |
E806472
|
entity |
| Predicate | sharesEducationSystemWith |
P12838
|
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, sharesEducationSystemWith, Canton of Fribourg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesEducationSystemWith Context triple: [Villaz-Saint-Pierre, sharesEducationSystemWith, Canton of Fribourg]
-
A.
sharesSchoolSystemServicesWith
chosen
Indicates that two entities use or are supported by the same school system services or infrastructure.
-
B.
sharesCurriculumWith
Indicates that two educational programs or courses use the same or substantially overlapping curriculum content.
-
C.
sharesInstitution
Indicates that two entities are affiliated with or belong to the same institution.
-
D.
shareHigherEducationFeature
Indicates that two entities have at least one higher-education-related attribute or characteristic in common.
-
E.
educationSystem
Indicates the relationship in which an entity is part of, governed by, or operates within a particular system or structure of education.
- 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_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 30, 2026, 10:34 p.m.