Triple
T14378005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sámi languages |
E356523
|
entity |
| Predicate | haveOfficialStatusIn |
P18869
|
FINISHED |
| Object | parts of Norway |
—
|
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: parts of Norway | Statement: [Sámi languages, haveOfficialStatusIn, parts of Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveOfficialStatusIn Context triple: [Sámi languages, haveOfficialStatusIn, parts of Norway]
-
A.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
B.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
C.
hasFormalStatus
chosen
Indicates that an entity possesses an officially recognized or legally defined status within a formal system or context.
-
D.
coOfficialStatusIn
Indicates that two or more entities share the same official status within a specified context, such as a jurisdiction, organization, or system.
-
E.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900a67e08190ab1dcf36e6bb3405 |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.