Triple
T5349316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhmisch Aicha |
E124134
|
entity |
| Predicate | historicalLanguageOfName |
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: [Böhmisch Aicha, historicalLanguageOfName, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageOfName Context triple: [Böhmisch Aicha, historicalLanguageOfName, German]
-
A.
languageOfHistoricName
chosen
Indicates the language in which a historic or former name of an entity is expressed.
-
B.
historicalLanguageOfHierarchy
Indicates that a language served as the traditional or historically established language used by a particular hierarchy or hierarchical institution.
-
C.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
D.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
E.
historicalLanguageRegion
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860ea7088190ad7be14132927d17 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:01 p.m.