Triple
T34659810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ink Palace |
E890074
|
entity |
| Predicate | hasAlternativeLanguageOfName |
P63334
|
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: [Ink Palace, hasAlternativeLanguageOfName, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeLanguageOfName Context triple: [Ink Palace, hasAlternativeLanguageOfName, German]
-
A.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
B.
alternateLanguageName
chosen
Indicates that an entity has an additional name or label in a different language from its primary or default name.
-
C.
mainLanguageOfAlternativeName
Indicates that a specified language is the primary language in which an alternative name for an entity is expressed.
-
D.
hasEnglishNameVariant
Indicates that one entity is an alternative or variant form of another entity’s name specifically in the English language.
-
E.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.