Triple
T5198002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ripuarian |
E117319
|
entity |
| Predicate | borderedByDialectArea |
P10768
|
FINISHED |
| Object | Limburgish area |
—
|
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: Limburgish area | Statement: [Ripuarian, borderedByDialectArea, Limburgish area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByDialectArea Context triple: [Ripuarian, borderedByDialectArea, Limburgish area]
-
A.
borderDialectOf
Indicates a dialect that is spoken in a border area and is linguistically associated with or derived from a particular neighboring language or dialect.
-
B.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
C.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
D.
borderRegionOf
chosen
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
E.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
- 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_69bd4462ed04819084fcb01eb9d2fa74 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.