Triple
T27273128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wezembeek-Oppem |
E688109
|
entity |
| Predicate | hasLocalServicesLanguage |
P179469
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Wezembeek-Oppem, hasLocalServicesLanguage, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalServicesLanguage Context triple: [Wezembeek-Oppem, hasLocalServicesLanguage, Dutch]
-
A.
hasMajorityLanguageServices
Indicates that one language is used for the majority of services or service interactions within a given context or system.
-
B.
hasStandardLanguageNearby
Indicates that a standard or commonly used language is present in close proximity to the referenced entity.
-
C.
hasCustomerServiceLanguage
Indicates that an entity provides customer service in a specified language or set of languages.
-
D.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
E.
hasPrimaryLanguageNearby
Indicates that an entity is associated with a primary language that is predominantly used or present in its immediate geographic or contextual vicinity.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 11 a.m.