Triple
T228134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian language |
E4355
|
entity |
| Predicate | ISO639-3MacrolanguageCode |
P5197
|
FINISHED |
| Object | nor |
—
|
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: nor | Statement: [Norwegian language, ISO639-3MacrolanguageCode, nor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3MacrolanguageCode Context triple: [Norwegian language, ISO639-3MacrolanguageCode, nor]
-
A.
languageCodeISO639-2
chosen
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
B.
ISO639_3Status
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
-
C.
languageCodeISO639-1
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
D.
languageFamilyCode
Indicates the language family to which a given language belongs, represented by a standardized code.
-
E.
glottocode
Indicates the standardized Glottolog code that uniquely identifies the language or dialect associated with an entity.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.