Triple
T31604769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semsales |
E806450
|
entity |
| Predicate | usesISO3166-2 |
P164530
|
FINISHED |
| Object | CH-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: CH-FR | Statement: [Semsales, usesISO3166-2, CH-FR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesISO3166-2 Context triple: [Semsales, usesISO3166-2, CH-FR]
-
A.
usesISO3166-2Code
chosen
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
B.
hasISO3166-2CodePrefix
Indicates that one entity’s ISO 3166-2 code begins with, or is prefixed by, the code of another entity.
-
C.
associatedSubdivisionISO3166-1Alpha2
Indicates that a subdivision (such as a state or province) is associated with a specific country identified by its ISO 3166-1 alpha-2 code.
-
D.
ISO3166-2RegionCode
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.
-
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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:34 p.m.