Triple
T3632328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flemings |
E76984
|
entity |
| Predicate | usesDialects |
P23892
|
FINISHED |
| Object | West Flemish |
—
|
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: West Flemish | Statement: [Flemings, usesDialects, West Flemish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDialects Context triple: [Flemings, usesDialects, West Flemish]
-
A.
usesDialect
chosen
Indicates that one entity communicates or expresses itself using the specific dialect associated with another entity.
-
B.
hasDialects
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
-
C.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
D.
affectsDialect
Indicates that one entity influences or changes the dialect used or spoken by another entity.
-
E.
isBasedOnDialect
Indicates that something (such as a language variety, system, or representation) is derived from, structured around, or primarily influenced by a particular dialect.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30251d881908284edeb7fe69ad8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.