Triple
T38413949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Hessian |
E901552
|
entity |
| Predicate | belongsToDialectArea |
P30285
|
FINISHED |
| Object | Rhenish fan area |
—
|
NE NERFINISHED |
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: Rhenish fan area | Statement: [Central Hessian, belongsToDialectArea, Rhenish fan area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToDialectArea Context triple: [Central Hessian, belongsToDialectArea, Rhenish fan area]
-
A.
relatedDialectArea
Indicates that one dialect area is geographically, historically, or linguistically connected to another dialect area.
-
B.
containsDialectRegion
chosen
Indicates that one linguistic variety or dataset includes or covers a specific dialect region within its scope.
-
C.
centerOfDialectArea
Indicates the location that serves as the central or focal point of a particular dialect area.
-
D.
consideredDialectOf
Indicates that one language variety is regarded as a dialect of another language or linguistic standard.
-
E.
relatedDialect
Indicates that one dialect has a recognized linguistic relationship or close affinity to another 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: May 3, 2026, 4:31 p.m.