Triple
T32548975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian language movement |
E831922
|
entity |
| Predicate | opposedLanguageStandard |
P185235
|
FINISHED |
| Object | Danish |
—
|
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: Danish | Statement: [Norwegian language movement, opposedLanguageStandard, Danish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedLanguageStandard Context triple: [Norwegian language movement, opposedLanguageStandard, Danish]
-
A.
sharedLanguageStandard
Indicates that the related entities use or conform to the same language standard or specification.
-
B.
competingStandard
chosen
Indicates that one standard exists in rivalry or conflict with another standard, typically addressing the same need or domain in an incompatible or alternative way.
-
C.
opposedStyle
Indicates that one entity’s style is in opposition or contrast to the style of another entity.
-
D.
contrastsWithMajorityLanguage
Indicates that one language or linguistic feature is notably different from, and stands in opposition to, the dominant or majority language in a given context.
-
E.
forbadeLanguage
Indicates that one entity prohibited another entity from using or expressing a particular language.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:02 a.m.