Triple
T18013452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa clan |
E430939
|
entity |
| Predicate | dispossessionEvent |
P119604
|
FINISHED |
| Object | abolition of the shogunate |
—
|
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: abolition of the shogunate | Statement: [Tokugawa clan, dispossessionEvent, abolition of the shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispossessionEvent Context triple: [Tokugawa clan, dispossessionEvent, abolition of the shogunate]
-
A.
dispossessedBy
Indicates that one entity has been deprived of possession, control, or ownership of something as a result of the actions of another entity.
-
B.
expulsionEvent
Indicates an event in which an entity is formally forced to leave or is removed from a place, group, or institution.
-
C.
displacementEvent
Indicates an event in which an entity is moved or shifted from its original position or location to a different one.
-
D.
abolitionEvent
chosen
Indicates an event or action through which a law, practice, institution, or condition is formally ended or abolished.
-
E.
timePeriodOfMajorDispossession
Indicates the time span during which the primary or most significant act of dispossession occurred.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b521befc81908dff44f19aa3d580 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.