Triple
T18929001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper German Reichskreis |
E463047
|
entity |
| Predicate | dissolvedEvent |
P42155
|
FINISHED |
| Object | dissolution of the Holy Roman Empire |
—
|
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: dissolution of the Holy Roman Empire | Statement: [Upper German Reichskreis, dissolvedEvent, dissolution of the Holy Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedEvent Context triple: [Upper German Reichskreis, dissolvedEvent, dissolution of the Holy Roman Empire]
-
A.
dissolvedAfterEvent
Indicates that an entity ceased to exist, function, or remain intact as a direct consequence of a specified event occurring beforehand.
-
B.
dissolvedDueTo
chosen
Indicates that a relationship, agreement, or entity came to an end as a result of a specified cause or event.
-
C.
dissolvedBefore
Indicates that one entity ceased to exist, function, or remain in solution at an earlier time than another entity.
-
D.
eventAfterDissolution
Indicates that one event occurs after the dissolution or termination of another entity, such as an organization, agreement, or relationship.
-
E.
dissolvedOnOrAround
Indicates that an entity ceased to exist, function, or remain in force on or approximately around a specified date.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bea84081908fbe657fb4657c0b |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.