Triple
T13422805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial District of Poznań |
E313398
|
entity |
| Predicate | formerOfficialLanguageOfToponym |
P91885
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Imperial District of Poznań, formerOfficialLanguageOfToponym, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerOfficialLanguageOfToponym Context triple: [Imperial District of Poznań, formerOfficialLanguageOfToponym, German]
-
A.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
B.
formerOfficialNameLanguage
chosen
Indicates the language in which an entity’s former official name was expressed.
-
C.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaecf13748190ae40c7b95164f914 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.