Triple
T29533418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikeda clan |
E749267
|
entity |
| Predicate | domainAbolition |
P156750
|
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: [Ikeda clan, domainAbolition, Abolition of the han system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainAbolition Context triple: [Ikeda clan, domainAbolition, Abolition of the han system]
-
A.
formerDomain
Indicates that one entity was previously the domain or area of control, influence, or ownership of another entity, but no longer is.
-
B.
abolishedAsDomainSystem
chosen
Indicates that a particular system, previously used as a domain or governing framework, has been officially abolished or discontinued.
-
C.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
D.
willBeAbolished
Indicates that the referenced entity is expected or planned to cease to exist or be officially terminated in the future.
-
E.
titleAbolishedBy
Indicates that a particular title or rank was formally eliminated or discontinued by a specified authority, event, or legal act.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66cc44fd0819081167945377cf3c4 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:55 p.m.