Triple
T15356024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lego.com |
E367170
|
entity |
| Predicate | offersLanguageVersion |
P55469
|
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: [Lego.com, offersLanguageVersion, Danish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersLanguageVersion Context triple: [Lego.com, offersLanguageVersion, Danish]
-
A.
officialLanguageVersion
Indicates that one language variant is the officially recognized form or version used for formal or administrative purposes in relation to another language or context.
-
B.
languageVersions
chosen
Indicates a relationship where one entity represents a specific version or variant of a language associated with another entity.
-
C.
supportsLanguageVersion
Indicates that one entity provides compatibility with, or can correctly operate using, a specified version of a language.
-
D.
requiresLanguageVersion
Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2c00648190ae2325e1ee58dcfd |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.