Triple
T8773261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL |
E208515
|
entity |
| Predicate | regionCodeFormat |
P3820
|
FINISHED |
| Object | two-letter Latin alphabet code |
—
|
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: two-letter Latin alphabet code | Statement: [KL, regionCodeFormat, two-letter Latin alphabet code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCodeFormat Context triple: [KL, regionCodeFormat, two-letter Latin alphabet code]
-
A.
regionCodeType
chosen
Indicates the classification or format type used for a given region code within a coding or identification system.
-
B.
countryCodeFormat
Indicates the standardized structure or pattern in which a country's code must be represented.
-
C.
regionCodeLevel
Indicates the hierarchical level or granularity associated with a given regional code within an administrative or geographic coding system.
-
D.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
E.
countryCodePart
Indicates that one entity is a segment or component of a standardized country code associated with another entity.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f2dc87c8190be0597a260d95a0b |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.