Triple
T4713769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .sm |
E104580
|
entity |
| Predicate | iso3166Mapping |
P208
|
FINISHED |
| Object | ISO 3166-1 alpha-2 code SM |
—
|
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: ISO 3166-1 alpha-2 code SM | Statement: [.sm, iso3166Mapping, ISO 3166-1 alpha-2 code SM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iso3166Mapping Context triple: [.sm, iso3166Mapping, ISO 3166-1 alpha-2 code SM]
-
A.
linkedToISO3166-2CodesOf
Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
-
B.
ISOCode
chosen
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
C.
ISO3166Basis
Indicates that one standard, classification, or designation is defined or derived based on the ISO 3166 country code system.
-
D.
sharesISO3166CodeWith
Indicates that two entities are associated with and use the same ISO 3166 country code.
-
E.
iso3166CodeBasedOn
Indicates that one code or designation is derived from, corresponds to, or is assigned on the basis of a specific ISO 3166 country or region code.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.