Triple
T25293247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukita clan |
E634145
|
entity |
| Predicate | lostDomainAfter |
P78345
|
FINISHED |
| Object | Battle of Sekigahara |
—
|
NE NERFINISHED |
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: Battle of Sekigahara | Statement: [Ukita clan, lostDomainAfter, Battle of Sekigahara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostDomainAfter Context triple: [Ukita clan, lostDomainAfter, Battle of Sekigahara]
-
A.
lostSupportOf
Indicates that one entity no longer has the backing, approval, or endorsement of another entity that previously supported it.
-
B.
lostAuthorityOver
chosen
Indicates that an entity no longer holds control, power, or decision-making authority over another entity or domain it previously governed.
-
C.
lostStatus
Indicates that an entity has transitioned into a state of being lost, missing, or no longer in its expected or intended possession or location.
-
D.
lostDuring
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
lostPowerAfter
Indicates that one entity ceased to have power or electricity following an event associated with another entity.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcf4bc88190a9ffaa3b07d5b881 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.