Triple
T2973795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Breslau |
E80345
|
entity |
| Predicate | reorganizationYear |
P44327
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [University of Breslau, reorganizationYear, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reorganizationYear Context triple: [University of Breslau, reorganizationYear, 1811]
-
A.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
-
B.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
C.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
D.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
E.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
- F. None of above. chosen
Provenance (4 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9987bb6c8190adfb447b76276962 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:58 p.m.