Triple
T5953075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaumburg, Lower Saxony, Germany |
E132443
|
entity |
| Predicate | dissolutionCentury |
P10303
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Schaumburg, Lower Saxony, Germany, dissolutionCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolutionCentury Context triple: [Schaumburg, Lower Saxony, Germany, dissolutionCentury, 19th century]
-
A.
dissolutionProcess
Indicates the process or sequence of actions by which something (such as a substance, organization, or relationship) is broken down, disbanded, or brought to an end.
-
B.
dissolutionTime
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
-
C.
dissolutionFollowedBy
Indicates that one dissolution event occurs first and is directly succeeded by another specified event or state.
-
D.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
-
E.
century
chosen
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.