Triple
T34275037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig II. von Ungarn und Böhmen |
E879428
|
entity |
| Predicate | NameInDeutsch |
P22792
|
FINISHED |
| Object | Ludwig II. von Ungarn und Böhmen |
—
|
NE NERFINISHED |
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: Ludwig II. von Ungarn und Böhmen | Statement: [Ludwig II. von Ungarn und Böhmen, NameInDeutsch, Ludwig II. von Ungarn und Böhmen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NameInDeutsch Context triple: [Ludwig II. von Ungarn und Böhmen, NameInDeutsch, Ludwig II. von Ungarn und Böhmen]
-
A.
nameInGerman
chosen
Indicates that an entity is known or referred to by a specific name in the German language.
-
B.
equivalentSurnameInGerman
Indicates that two surnames are equivalent to each other when translated into or represented in the German language.
-
C.
nameInFrench
Indicates that an entity is known or referred to by a specific name expressed in the French language.
-
D.
nameInEsperanto
Indicates that an entity’s name is expressed in the Esperanto language.
-
E.
nameInHungarian
Indicates that one entity is the Hungarian-language name or designation of 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:56 a.m.