Triple
T8457757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bragança |
E199961
|
entity |
| Predicate | regionalLanguagePresence |
P10892
|
FINISHED |
| Object | Mirandese nearby |
—
|
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: Mirandese nearby | Statement: [Bragança, regionalLanguagePresence, Mirandese nearby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalLanguagePresence Context triple: [Bragança, regionalLanguagePresence, Mirandese nearby]
-
A.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
B.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
C.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
D.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
- 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49064f881909391d565b97e9886 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.