Triple
T21006225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES618 |
E517419
|
entity |
| Predicate | ISO3166-2Correspondence |
P27650
|
FINISHED |
| Object | ES-SE |
—
|
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: ES-SE | Statement: [ES618, ISO3166-2Correspondence, ES-SE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO3166-2Correspondence Context triple: [ES618, ISO3166-2Correspondence, ES-SE]
-
A.
ISO3166-2DifferentFrom
Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
-
B.
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.
-
C.
ISO3166Relation
Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
-
D.
ISO3166Basis
Indicates that one standard, classification, or designation is defined or derived based on the ISO 3166 country code system.
-
E.
linkedToISO3166-2CodesOf
chosen
Indicates a relationship where an entity is associated with, or mapped to, specific ISO 3166-2 subdivision codes that represent its corresponding administrative regions.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3c05a481908d25de2a63a4cdbe |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.