Triple
T30783241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsberg in Ostpreußen |
E783879
|
entity |
| Predicate | pre1945OfficialName |
P159981
|
FINISHED |
| Object | Landsberg i. Ostpr. |
—
|
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: Landsberg i. Ostpr. | Statement: [Landsberg in Ostpreußen, pre1945OfficialName, Landsberg i. Ostpr.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pre1945OfficialName Context triple: [Landsberg in Ostpreußen, pre1945OfficialName, Landsberg i. Ostpr.]
-
A.
pre1945Name
chosen
Indicates that the associated name is the one used for an entity prior to the year 1945.
-
B.
countryBefore1940
Indicates that the specified country existed or was recognized as such prior to the year 1940.
-
C.
regionBefore1945
Indicates that one region existed or was defined in a particular way prior to the year 1945.
-
D.
preColonialNameFor
Indicates that one name was used for something in the pre-colonial period and refers to the same entity later known by a different (typically colonial or post-colonial) name.
-
E.
pre1948Status
Indicates the status or condition of an entity as it existed prior to the year 1948.
- 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_69f68fe5d3f0819090561db2cc56f1f3 |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.