Triple
T22382511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asano clan |
E553309
|
entity |
| Predicate | consequenceOfNotableEvent |
P145803
|
FINISHED |
| Object | confiscation of Ako Domain |
—
|
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: confiscation of Ako Domain | Statement: [Asano clan, consequenceOfNotableEvent, confiscation of Ako Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfNotableEvent Context triple: [Asano clan, consequenceOfNotableEvent, confiscation of Ako Domain]
-
A.
significantEventConsequence
Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
-
B.
impactOfNotableEvent
chosen
Indicates the causal influence or consequences that a specific notable event has on an entity, situation, or outcome.
-
C.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
D.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.