Triple
T17659313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | סקווירא |
E440207
|
entity |
| Predicate | languageOfLocalJews |
P35871
|
FINISHED |
| Object | יידיש |
—
|
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: יידיש | Statement: [סקווירא, languageOfLocalJews, יידיש]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocalJews Context triple: [סקווירא, languageOfLocalJews, יידיש]
-
A.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
B.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
C.
ethnicLanguageStatus
chosen
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
D.
hasSignificantJewishCommunity
Indicates that a place or entity possesses a notably large, influential, or historically important Jewish community.
-
E.
historicalMinorityLanguage
Indicates that a language has historically been used by a minority group within a given region or population, even if it may no longer be widely spoken there.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea469448190b2753571f8493aef |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:39 a.m.