Triple
T2132755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of West Prussia |
E46578
|
entity |
| Predicate | dateReestablished |
P9113
|
FINISHED |
| Object | 1878 |
—
|
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: 1878 | Statement: [Province of West Prussia, dateReestablished, 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReestablished Context triple: [Province of West Prussia, dateReestablished, 1878]
-
A.
reestablishedInYear
chosen
Indicates that an entity, previously existing and then discontinued or dissolved, was brought back into existence or operation in the specified year.
-
B.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
C.
establishedAt
Indicates the specific time or date at which something (such as an organization, system, or entity) was founded or brought into existence.
-
D.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
E.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba0c42c8190ab3ce4bbf1531ee1 |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.