Triple
T32408034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Postcode.nl database |
E828134
|
entity |
| Predicate | sectorUsedIn |
P162915
|
FINISHED |
| Object | e-commerce |
—
|
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: e-commerce | Statement: [Postcode.nl database, sectorUsedIn, e-commerce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorUsedIn Context triple: [Postcode.nl database, sectorUsedIn, e-commerce]
-
A.
sectorUsage
chosen
Indicates how a particular sector is utilized or engaged in a given context or activity.
-
B.
sectorIncludes
Indicates that a broader sector encompasses or contains a specified sub-sector, area, or component within its scope.
-
C.
sectorBase
Indicates that one entity serves as the primary base or foundational location for operations within a particular sector of another entity.
-
D.
sectorServed
Indicates the industry or economic sector that an entity primarily serves or targets with its activities, products, or services.
-
E.
sideUsedBy
Indicates that a particular side or aspect of something is utilized or employed by a specified 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c24ca0f08190a5b2c1d32205eaee |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.