Triple
T30783240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsberg in Ostpreußen |
E783879
|
entity |
| Predicate | germanExonymFor |
P22792
|
FINISHED |
| Object | Górowo Iławeckie |
—
|
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: Górowo Iławeckie | Statement: [Landsberg in Ostpreußen, germanExonymFor, Górowo Iławeckie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: germanExonymFor Context triple: [Landsberg in Ostpreußen, germanExonymFor, Górowo Iławeckie]
-
A.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
countryNameGerman
Indicates the German-language name used to refer to a given country.
-
C.
nameInGerman
chosen
Indicates that an entity is known or referred to by a specific name in the German language.
-
D.
exonymStatus
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
E.
EuropeanNameVariant
Indicates that one name is a variant or alternative form of another name as used in a European language or cultural context.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:41 p.m.