Triple
T15403994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steenwijk |
E368400
|
entity |
| Predicate | isRegionalServiceCenter |
P50530
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Steenwijk, isRegionalServiceCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalServiceCenter Context triple: [Steenwijk, isRegionalServiceCenter, true]
-
A.
isRegionalServiceCentre
chosen
Indicates that an entity functions as a regional service center responsible for providing services or support to a defined geographic area.
-
B.
isServiceCentreFor
Indicates that one entity functions as a service center that provides support, maintenance, or related services for another entity.
-
C.
hasServiceCenter
Indicates that an entity maintains or is associated with a service center that provides support, repair, or maintenance services.
-
D.
isReferralCenterFor
Indicates that one entity serves as a designated center to which other entities send or direct cases, clients, or tasks for specialized services or handling.
-
E.
hasRegionalServices
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8fde64819082ec0c68df305561 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.