Triple
T17286603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veluws dialect |
E419669
|
entity |
| Predicate | tendsToBeReplacedBy |
P82114
|
FINISHED |
| Object | Standard Dutch in formal contexts |
—
|
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: Standard Dutch in formal contexts | Statement: [Veluws dialect, tendsToBeReplacedBy, Standard Dutch in formal contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tendsToBeReplacedBy Context triple: [Veluws dialect, tendsToBeReplacedBy, Standard Dutch in formal contexts]
-
A.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
B.
oftenReplacedBy
chosen
Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
-
C.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
D.
partlyReplacedBy
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
E.
indirectlyReplacedBy
Indicates that one entity has been superseded or taken over by another entity through one or more intermediate replacements, rather than by a direct, immediate substitution.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4378024988190aac6aec006f8f7a1 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.