Triple
T3882441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nynorsk |
E92855
|
entity |
| Predicate | hasWritingStandardSince |
P7432
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Nynorsk, hasWritingStandardSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWritingStandardSince Context triple: [Nynorsk, hasWritingStandardSince, 20th century]
-
A.
hasOfficialWrittenStandard
Indicates that there exists an officially recognized and codified written standard governing how something (e.g., a language or system) should be represented in writing.
-
B.
hasStandardOrthographySince
chosen
Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
-
C.
introducedInStandard
Indicates that something (such as a concept, feature, or element) was first defined or formally specified in a particular standard.
-
D.
standardizedSince
Indicates that something has been formally standardized starting from a specific point in time.
-
E.
hasSoftwareStandard
Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.