Triple
T16901490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawitsch |
E424447
|
entity |
| Predicate | hasLanguageOfLocalPopulation |
P77346
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Rawitsch, hasLanguageOfLocalPopulation, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfLocalPopulation Context triple: [Rawitsch, hasLanguageOfLocalPopulation, Polish]
-
A.
hasLanguageInhabitants
chosen
Indicates that a particular language is spoken or used by the inhabitants of a specified place or region.
-
B.
hasIndigenousLanguageSpoken
Indicates that an entity is associated with an indigenous language that is or was spoken by it or within its context.
-
C.
majorityLanguageOf
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
D.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
E.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dc7cf08190ad935935d8daf1d0 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.