Triple
T15524158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SZFO |
E369039
|
entity |
| Predicate | ISO3166_2Code |
P42695
|
FINISHED |
| Object | RU-SZFO |
—
|
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: RU-SZFO | Statement: [SZFO, ISO3166_2Code, RU-SZFO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO3166_2Code Context triple: [SZFO, ISO3166_2Code, RU-SZFO]
-
A.
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.
-
B.
ISO3166-2DifferentFrom
Indicates that two ISO 3166-2 subdivision codes are explicitly distinct and should not be considered equivalent or interchangeable.
-
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.
associatedCountrySubdivisionCode
Indicates the specific administrative region or subdivision code within a country that is linked to or relevant for the given entity.
-
E.
ISO3166Relation
Indicates a relationship that associates an entity with its corresponding ISO 3166 country or region code as defined by the international standard.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e04143bda08190a2dee44918c1ad1c |
completed | April 16, 2026, 1:54 a.m. |
| PD | Predicate disambiguation | batch_69ded28ab0588190a47a9090d1238707 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 4:05 a.m.