Triple
T33367095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Fribourg |
E854383
|
entity |
| Predicate | hasPrimaryLanguagesGroup |
P3349
|
FINISHED |
| Object | Romance and Germanic |
—
|
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: Romance and Germanic | Statement: [municipality of Fribourg, hasPrimaryLanguagesGroup, Romance and Germanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLanguagesGroup Context triple: [municipality of Fribourg, hasPrimaryLanguagesGroup, Romance and Germanic]
-
A.
hasLanguageGroup
chosen
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
B.
hasPrimaryLanguage1
Indicates that an entity’s main or most commonly used language is the specified language.
-
C.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
D.
primaryLanguageGroup
Indicates that the related entities share or belong to the same main or dominant language group.
-
E.
hasPrimaryTraditionalLanguage
Indicates that one entity is the main or principal traditional language associated with another entity.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: May 1, 2026, 1:35 a.m.