Triple
T35906527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Lechitic |
E1038486
|
entity |
| Predicate | chieflyRepresentedBy |
P86059
|
FINISHED |
| Object | Kashubian language |
—
|
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: Kashubian language | Statement: [Southern Lechitic, chieflyRepresentedBy, Kashubian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chieflyRepresentedBy Context triple: [Southern Lechitic, chieflyRepresentedBy, Kashubian language]
-
A.
primarilyRepresentedBy
chosen
Indicates that one entity serves as the main or most characteristic representation or depiction of another entity.
-
B.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
C.
representedInPartBy
Indicates that something is partially depicted, expressed, or captured within another thing, but not in its entirety.
-
D.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
-
E.
isRepresentiveOf
Indicates that one entity serves as an official agent, spokesperson, or proxy acting on behalf of 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa6fd79c8190b1a70068ace78068 |
completed | May 3, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:07 p.m.