Triple
T17562542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaczawa River basin |
E427727
|
entity |
| Predicate | historicalLanguageOfToponymy |
P52208
|
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: [Kaczawa River basin, historicalLanguageOfToponymy, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageOfToponymy Context triple: [Kaczawa River basin, historicalLanguageOfToponymy, German]
-
A.
languageOfHistoricName
chosen
Indicates the language in which a historic or former name of an entity is expressed.
-
B.
hasLanguageOfToponym
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
C.
regionHistoricalEthnonym
Indicates that a region is historically known or referred to by a particular ethnonym associated with a people or ethnic group.
-
D.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
-
E.
influenceOnToponymy
Indicates that one entity has affected or shaped the naming, form, or development of place names associated with 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456285c808190953a49e77366d8bd |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.