Triple
T3953356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VS |
E84918
|
entity |
| Predicate | ISO3166-2CodeForCanton |
P42695
|
FINISHED |
| Object | CH-VS |
—
|
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: CH-VS | Statement: [VS, ISO3166-2CodeForCanton, CH-VS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO3166-2CodeForCanton Context triple: [VS, ISO3166-2CodeForCanton, CH-VS]
-
A.
cantonCode
Indicates the specific administrative canton identifier associated with an entity or location.
-
B.
ISO3166-2RegionCode
chosen
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
-
C.
hasCanton
Indicates that an entity is administratively divided into, or associated with, a specific canton.
-
D.
includesCanton
Indicates that a larger administrative or geographic entity contains or encompasses a specific canton within its boundaries.
-
E.
countrySubdivision
Indicates that one geopolitical region is an administrative or territorial subdivision of a larger country.
- 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:30 p.m.