Triple
T30783223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsberg in Ostpreußen |
E783879
|
entity |
| Predicate | currentOfficialLanguageOfTown |
P96074
|
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: [Landsberg in Ostpreußen, currentOfficialLanguageOfTown, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentOfficialLanguageOfTown Context triple: [Landsberg in Ostpreußen, currentOfficialLanguageOfTown, Polish]
-
A.
hasOfficialLanguageOfLocation
chosen
Indicates that a location has a specified language recognized as its official language.
-
B.
previousOfficialLanguage
Indicates that one language formerly held official status in a country, region, or organization before being replaced or losing that status.
-
C.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
D.
declaresOfficialLanguageOf
Indicates that an authority formally designates a particular language as the official language of a specified entity or jurisdiction.
-
E.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 8:41 p.m.