Triple
T13765629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Lauenburg |
E330732
|
entity |
| Predicate | statusAfter1866 |
P110873
|
FINISHED |
| Object | Prussian district |
—
|
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: Prussian district | Statement: [Duchy of Lauenburg, statusAfter1866, Prussian district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1866 Context triple: [Duchy of Lauenburg, statusAfter1866, Prussian district]
-
A.
statusAfter1867
Indicates the status or condition an entity holds after the year 1867, typically in contrast to its status before that date.
-
B.
statusAfter1857
Indicates the condition or state of an entity as it existed after the year 1857, typically in contrast to its prior status.
-
C.
statusAfter1865
Indicates the condition or state of an entity as it existed after the year 1865.
-
D.
statusAfter1898
Indicates the condition or state that something or someone has after the year 1898.
-
E.
statusAfter1815
Indicates the status or condition of an entity as it existed after the year 1815.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0227f2c48190983ccc9395e4e7a2 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:10 p.m.