Triple
T18841860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterzing |
E460816
|
entity |
| Predicate | regionallyRecognizedLanguage |
P2982
|
FINISHED |
| Object | Ladin (in wider region) |
—
|
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: Ladin (in wider region) | Statement: [Sterzing, regionallyRecognizedLanguage, Ladin (in wider region)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyRecognizedLanguage Context triple: [Sterzing, regionallyRecognizedLanguage, Ladin (in wider region)]
-
A.
recognizedRegionalLanguage
chosen
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
B.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
C.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
D.
languageFamilyRegion
Indicates the geographic region or area in which a language family is predominantly found or historically associated.
-
E.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8ea35c88190af6659551ad18130 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.