Triple
T20500364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galar |
E503282
|
entity |
| Predicate | languageInGame |
P18209
|
FINISHED |
| Object | Galarian language-inspired English 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: Galarian language-inspired English dialect | Statement: [Galar, languageInGame, Galarian language-inspired English dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageInGame Context triple: [Galar, languageInGame, Galarian language-inspired English dialect]
-
A.
languageCategory
Indicates the classification relationship where a language is assigned to a particular linguistic or functional category.
-
B.
languageOfTheme
Indicates that a particular language is used to express, describe, or label a given theme or subject.
-
C.
languageUse
chosen
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
D.
testLanguage
Indicates that an entity uses or is associated with a particular language for testing or evaluation purposes.
-
E.
governingLanguage
Indicates the language that holds official or authoritative status over a given entity, such as a region, organization, or document.
- 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc10cd08190915b6c29c6473f77 |
completed | April 20, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e59fcdf6e08190a604204615dc56e6 |
completed | April 20, 2026, 3:38 a.m. |
Created at: April 16, 2026, 11:35 a.m.