Triple
T36763970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uesugi Kagetora |
E908283
|
entity |
| Predicate | statusInClan |
P28158
|
FINISHED |
| Object | adopted heir candidate of Uesugi Kenshin |
—
|
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: adopted heir candidate of Uesugi Kenshin | Statement: [Uesugi Kagetora, statusInClan, adopted heir candidate of Uesugi Kenshin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInClan Context triple: [Uesugi Kagetora, statusInClan, adopted heir candidate of Uesugi Kenshin]
-
A.
hasClanStatus
chosen
Indicates that an entity holds a specific role, rank, or membership status within a clan or clan-like group.
-
B.
clanReputation
Indicates the perceived status or esteem a clan holds within a community or among other clans based on its actions or history.
-
C.
hasClanChiefStatus
Indicates that an entity holds the role or status of being the chief or leader of a clan.
-
D.
hasMemberClan
Indicates that a group or organization includes a specific clan as one of its members.
-
E.
isPrincipalClanOf
Indicates that one clan holds primary or leading status over another clan within a hierarchical or organizational structure.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:12 p.m.