Triple
T9018030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDE community |
E215643
|
entity |
| Predicate | hasLocalizationTeam |
P5562
|
FINISHED |
| Object | many language teams worldwide |
—
|
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: many language teams worldwide | Statement: [KDE community, hasLocalizationTeam, many language teams worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalizationTeam Context triple: [KDE community, hasLocalizationTeam, many language teams worldwide]
-
A.
localizationBy
Indicates a relationship where one entity determines, specifies, or constrains the spatial or contextual location of another entity.
-
B.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
C.
usesLocalLanguageVariant
Indicates that an entity employs a region-specific or localized form of a language rather than a standard or global variant.
-
D.
supportsTeam
Indicates that one entity provides backing, assistance, or endorsement to a particular team.
-
E.
isLocalizable
Indicates that something can be adapted or translated to different languages or locales without losing its intended function or meaning.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a3ef98081909e66372a89f881b9 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.