Triple
T33793766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freiburg |
E866007
|
entity |
| Predicate | hasCantonAbbreviation |
P28599
|
FINISHED |
| Object | FR |
—
|
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: FR | Statement: [Freiburg, hasCantonAbbreviation, FR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCantonAbbreviation Context triple: [Freiburg, hasCantonAbbreviation, FR]
-
A.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
B.
cantonCode
chosen
Indicates the specific administrative canton identifier associated with an entity or location.
-
C.
usesCanton
Indicates that one entity employs or applies a specific canton (administrative region or heraldic area) in its structure, context, or operations.
-
D.
includesCanton
Indicates that a larger administrative or geographic entity contains or encompasses a specific canton within its boundaries.
-
E.
denotesCanton
Indicates that one entity is the canton (administrative subdivision) to which another entity belongs or with which it is associated.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 1:46 a.m.