Triple
T25302747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampenhout |
E634394
|
entity |
| Predicate | NISCode |
P144234
|
FINISHED |
| Object | 23038 |
—
|
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: 23038 | Statement: [Kampenhout, NISCode, 23038]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NISCode Context triple: [Kampenhout, NISCode, 23038]
-
A.
NAICSCode
Indicates that an entity is classified under a specific North American Industry Classification System (NAICS) code, defining its primary type of economic activity.
-
B.
regionCodeNIS
chosen
Indicates the standardized NIS (National Institute of Statistics) regional code assigned to the entity’s geographic area.
-
C.
SICCode
Indicates the standardized industrial classification code that categorizes the primary type of economic activity associated with an entity or relationship.
-
D.
NOCCode
Indicates the standardized occupational classification code assigned to a job or role within the National Occupational Classification system.
-
E.
sectorCode
Indicates the classification code that identifies the economic or organizational sector associated with an entity or activity.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f493968b5c8190bc0108a23b81b38a |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:25 p.m.