Triple
T17610972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 3166-2:CH |
E428963
|
entity |
| Predicate | usesAlpha2CountryCode |
P42506
|
FINISHED |
| Object | CH |
—
|
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 | Statement: [ISO 3166-2:CH, usesAlpha2CountryCode, CH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAlpha2CountryCode Context triple: [ISO 3166-2:CH, usesAlpha2CountryCode, CH]
-
A.
isUniqueWithinISO3166-1Alpha2
Indicates that the referenced entity is unique within the scope defined by a specific ISO 3166-1 alpha-2 country code.
-
B.
useCountry
Indicates that one entity utilizes or operates within the jurisdiction, systems, or context of a specified country.
-
C.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
D.
associatedCountryCode
chosen
Indicates that there is a relationship linking something to the country identified by the given country code.
-
E.
ISO3166-2DifferentFrom
Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d2d294881908380b2ab0b4d2503 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.