Triple
T11287018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaustein station |
E267218
|
entity |
| Predicate | hasLanguageOfPlaceName |
P24399
|
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: [Blaustein station, hasLanguageOfPlaceName, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfPlaceName Context triple: [Blaustein station, hasLanguageOfPlaceName, German]
-
A.
hasLanguageOfToponym
chosen
Indicates that a place name (toponym) is expressed in or associated with a particular language.
-
B.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
C.
hasOfficialLanguageOfLocation
Indicates that a location has a specified language recognized as its official language.
-
D.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
E.
hasDemonymLanguage
Indicates that a language is used as the demonym (people’s name or adjective of nationality) for inhabitants of a particular place or group.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e986b0f08190a414749eaa7f1a5d |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.