Triple
T33732499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Münster im Elsass |
E864308
|
entity |
| Predicate | hatHistorischeSprache |
P26947
|
FINISHED |
| Object | Deutsch |
—
|
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: Deutsch | Statement: [Münster im Elsass, hatHistorischeSprache, Deutsch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatHistorischeSprache Context triple: [Münster im Elsass, hatHistorischeSprache, Deutsch]
-
A.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
B.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
C.
historicalLanguageCenter
chosen
Indicates that a location has served as a significant hub or focal point for the development, use, or study of a particular language in the past.
-
D.
historicalDialect
Indicates that one dialect is a historically earlier or ancestral form of another dialect.
-
E.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.