Triple
T15650327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsuwano Domain |
E376293
|
entity |
| Predicate | abolitionEvent |
P119604
|
FINISHED |
| Object | Abolition of the han system |
—
|
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 han system | Statement: [Tsuwano Domain, abolitionEvent, Abolition of the han system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolitionEvent Context triple: [Tsuwano Domain, abolitionEvent, Abolition of the han system]
-
A.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by 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.
repealedAfterEvent
Indicates that a law or regulation was repealed as a consequence of, or following, a specific event.
-
D.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
E.
permitsAbolitionOf
Indicates that one entity authorizes or allows the elimination, repeal, or discontinuation of another entity, condition, or practice.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eeed2d48190a7a8a618d90012d0 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.