Triple
T24151122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 8859-14 |
E598535
|
entity |
| Predicate | designedForLanguageGroup |
P75697
|
FINISHED |
| Object | Celtic languages |
—
|
NE NERFINISHED |
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: Celtic languages | Statement: [ISO/IEC 8859-14, designedForLanguageGroup, Celtic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForLanguageGroup Context triple: [ISO/IEC 8859-14, designedForLanguageGroup, Celtic languages]
-
A.
designedForLanguageFamily
chosen
Indicates that something (such as a tool, system, or resource) is specifically created or optimized to work with a particular language family rather than with individual languages in general.
-
B.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
C.
primaryLanguageGroup
Indicates that the related entities share or belong to the same main or dominant language group.
-
D.
developedForLanguage
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
-
E.
languageDesigned
Indicates that one entity created or developed the language used or associated with another entity.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.