Triple
T3270606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Prussia |
E68636
|
entity |
| Predicate | timeInGermanEmpire |
P38156
|
FINISHED |
| Object | 1871–1918 |
—
|
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: 1871–1918 | Statement: [West Prussia, timeInGermanEmpire, 1871–1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInGermanEmpire Context triple: [West Prussia, timeInGermanEmpire, 1871–1918]
-
A.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
-
B.
rankInGermanEmpireByArea
Indicates the ordinal position of an entity when all entities in the German Empire are ordered by their land area.
-
C.
regionBefore1945
chosen
Indicates that one region existed or was defined in a particular way prior to the year 1945.
-
D.
PrussianStrength
Indicates a relationship where an entity possesses or exhibits the military, political, or institutional power characteristic of Prussia.
-
E.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff349148190beae8c0994b7ad83 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.