Triple
T7275209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cala d'Or |
E163008
|
entity |
| Predicate | localVariantLanguage |
P73137
|
FINISHED |
| Object | Mallorquí |
—
|
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: Mallorquí | Statement: [Cala d'Or, localVariantLanguage, Mallorquí]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localVariantLanguage Context triple: [Cala d'Or, localVariantLanguage, Mallorquí]
-
A.
languageVariant
Indicates that one language is a variant, dialect, or localized form of another language.
-
B.
usesLocalLanguageVariant
chosen
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
C.
linguisticVariant
Indicates that one linguistic form is an alternative version or expression of another within the same or closely related language context.
-
D.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
E.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.