Triple
T36763968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uesugi Kagetora |
E908283
|
entity |
| Predicate | formerClan |
P202736
|
FINISHED |
| Object | Later Hōjō clan |
—
|
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: Later Hōjō clan | Statement: [Uesugi Kagetora, formerClan, Later Hōjō clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerClan Context triple: [Uesugi Kagetora, formerClan, Later Hōjō clan]
-
A.
formerRulingClan
Indicates that a clan previously held ruling power or authority over a group, territory, or polity but no longer does so.
-
B.
fatherClan
Indicates a kinship relationship where one entity belongs to, descends from, or is affiliated with the clan of the father of another entity.
-
C.
clanFamilyOf
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
D.
formerFamily
Indicates that the entities were once related as family members but are no longer considered part of the same family unit.
-
E.
notableClans
Indicates that there exists a significant or historically important clan associated with the subject.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b2b425a8819091ff65695e98c3af |
completed | May 10, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_6a00b06efa248190b2d16b4889185119 |
completed | May 10, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_6a00b2b3832c8190a1cb63e2a55639eb |
completed | May 10, 2026, 4:30 p.m. |
Created at: May 3, 2026, 4:12 p.m.