Triple
T37015750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ticino |
E916073
|
entity |
| Predicate | languageRegionOfSwitzerland |
P203346
|
FINISHED |
| Object | Italian-speaking Switzerland |
—
|
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: Italian-speaking Switzerland | Statement: [Ticino, languageRegionOfSwitzerland, Italian-speaking Switzerland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageRegionOfSwitzerland Context triple: [Ticino, languageRegionOfSwitzerland, Italian-speaking Switzerland]
-
A.
isVarietyOfLanguageWithOfficialStatusInSwitzerland
Indicates that a language variety holds official status as one of the recognized languages in Switzerland.
-
B.
spokenInCanton
Indicates that something (typically a language, phrase, or communication) is expressed using the Cantonese dialect.
-
C.
shortNameRomansh
Indicates that an entity has a short or abbreviated name expressed in the Romansh language.
-
D.
operatesInCanton
Indicates that an entity conducts its activities or has operational presence within a specified canton.
-
E.
governingCantonCapital
Indicates that a city serves as the capital and administrative seat of the specified canton.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0164b052608190adc93240dad50a06 |
completed | May 11, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_6a01637fd3ac8190970eb09650d1e659 |
completed | May 11, 2026, 5:05 a.m. |
| PDg | Predicate description generation | batch_6a0164af262c8190876c9eb2421ad9a7 |
completed | May 11, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:14 p.m.