Triple
T18108536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trøndelag Theatre |
E433410
|
entity |
| Predicate | languageVarietyUsed |
P41081
|
FINISHED |
| Object | Trøndersk dialect |
—
|
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: Trøndersk dialect | Statement: [Trøndelag Theatre, languageVarietyUsed, Trøndersk dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageVarietyUsed Context triple: [Trøndelag Theatre, languageVarietyUsed, Trøndersk dialect]
-
A.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
B.
primaryLanguageVariety
chosen
Indicates the main dialect or specific variety of a language that an entity primarily uses.
-
C.
hasLinguisticVariety
Indicates that one entity possesses or exhibits a particular linguistic variety in relation to another entity or context.
-
D.
workLanguageVariant
Indicates that one language variant of a work is related to another version of the same work, typically differing by language or localization.
-
E.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddbbfae88190aa77f498dbb9edcb |
completed | April 19, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.