Triple
T35906561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Lechitic |
E1038486
|
entity |
| Predicate | ISO639Representative |
P183959
|
FINISHED |
| Object | csb (Kashubian) |
—
|
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: csb (Kashubian) | Statement: [Southern Lechitic, ISO639Representative, csb (Kashubian)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639Representative Context triple: [Southern Lechitic, ISO639Representative, csb (Kashubian)]
-
A.
ISO639Language
Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
-
B.
ISO639-3ReferenceName
Indicates the standardized reference name assigned to a language in the ISO 639-3 coding system.
-
C.
ISO639-1Equivalent
Indicates that two language identifiers are equivalent according to the ISO 639-1 two-letter language code standard.
-
D.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
E.
ISO639-6Code
Indicates the standardized ISO 639-6 four-letter code that uniquely identifies a specific language variety or dialect.
- F. None of above. chosen
Provenance (4 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa33e0488190a135166bb67e1118 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:07 p.m.