Triple
T11788888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alemannic tribes |
E280339
|
entity |
| Predicate | regionShaped |
P101589
|
FINISHED |
| Object | language of southwestern German-speaking Europe |
—
|
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: language of southwestern German-speaking Europe | Statement: [Alemannic tribes, regionShaped, language of southwestern German-speaking Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionShaped Context triple: [Alemannic tribes, regionShaped, language of southwestern German-speaking Europe]
-
A.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
-
B.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
D.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
-
E.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.