Triple
T33717124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kang District |
E863904
|
entity |
| Predicate | hasISO3166-1Alpha2CodeCountry |
P176786
|
FINISHED |
| Object | AF |
—
|
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: AF | Statement: [Kang District, hasISO3166-1Alpha2CodeCountry, AF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO3166-1Alpha2CodeCountry Context triple: [Kang District, hasISO3166-1Alpha2CodeCountry, AF]
-
A.
hasISO3166-1Alpha2Country
chosen
Indicates that an entity is associated with a country identified by its ISO 3166-1 alpha-2 two-letter country code.
-
B.
hasISO3166-1NumericCode
Indicates that an entity is associated with a specific ISO 3166-1 numeric country code.
-
C.
usesISO3166-2Code
Indicates that an entity employs or references a subdivision identifier defined by the ISO 3166-2 standard.
-
D.
hasISO3166Alpha3Code
Indicates that an entity is associated with a specific three-letter country code defined by the ISO 3166-1 alpha-3 standard.
-
E.
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.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:44 a.m.