Triple
T31799828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwigskirche, Munich |
E811700
|
entity |
| Predicate | hasMassLanguage |
P202054
|
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: [Ludwigskirche, Munich, hasMassLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassLanguage Context triple: [Ludwigskirche, Munich, hasMassLanguage, German]
-
A.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
B.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
C.
hasMacrolanguage
Indicates that a language is part of, or grouped under, a broader macrolanguage that encompasses multiple closely related language varieties.
-
D.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
E.
hasOwnLanguage
Indicates that an entity possesses or uses a distinct language of its own.
- F. None of above. chosen
Provenance (4 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a004a8892c08190bcacb952ad737716 |
completed | May 10, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_6a004a44b4948190be4b3dbfce8da020 |
completed | May 10, 2026, 9:05 a.m. |
| PDg | Predicate description generation | batch_6a004a87bb908190a2bd164a60245f1d |
completed | May 10, 2026, 9:06 a.m. |
Created at: April 30, 2026, 11:41 p.m.