Triple
T103732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Pensionary |
E2095
|
entity |
| Predicate | abolishedWith |
P3903
|
FINISHED |
| Object | end of the Dutch Republic in 1795 |
—
|
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: end of the Dutch Republic in 1795 | Statement: [Grand Pensionary, abolishedWith, end of the Dutch Republic in 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedWith Context triple: [Grand Pensionary, abolishedWith, end of the Dutch Republic in 1795]
-
A.
dateAbolished
chosen
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
B.
dissolvedOrAbolished
Indicates that an organization, institution, or formal entity has been officially terminated, disbanded, or ceased to exist.
-
C.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
D.
reasonForAbolition
Indicates the cause, justification, or circumstances that led to something being formally ended or abolished.
-
E.
slaveryAbolishedBy
Indicates that an instance of slavery was ended, prohibited, or legally abolished by a particular agent, authority, or entity.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.