Triple
T10755865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KLGC |
E253691
|
entity |
| Predicate | regionCodePattern |
P95809
|
FINISHED |
| Object | K-prefix for contiguous United States |
—
|
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: K-prefix for contiguous United States | Statement: [KLGC, regionCodePattern, K-prefix for contiguous United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCodePattern Context triple: [KLGC, regionCodePattern, K-prefix for contiguous United States]
-
A.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
B.
regionCodeLevel
Indicates the hierarchical level or granularity associated with a given regional code within an administrative or geographic coding system.
-
C.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
D.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
E.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
- F. None of above. chosen
Provenance (4 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d72e9e224c819099d16aba77322812 |
completed | April 9, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:15 p.m.