Triple
T6656630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chōshū Domain |
E150960
|
entity |
| Predicate | abolishedInReform |
P30300
|
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: [Chōshū Domain, abolishedInReform, abolition of the han system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedInReform Context triple: [Chōshū Domain, abolishedInReform, abolition of the han system]
-
A.
abolishedDuring
chosen
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
B.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
C.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
-
D.
replacedInReform
Indicates that one entity was substituted or superseded by another as part of a formal reform or restructuring process.
-
E.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.