Triple
T26261792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senhime |
E656867
|
entity |
| Predicate | clanByMarriage |
P25212
|
FINISHED |
| Object | Honda 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: Honda clan | Statement: [Senhime, clanByMarriage, Honda clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clanByMarriage Context triple: [Senhime, clanByMarriage, Honda clan]
-
A.
connectedThroughMarriageVia
Indicates that two entities are related to each other by a marital connection that is mediated through one or more intermediate spouses or in-laws, rather than by a direct marriage between them.
-
B.
clanFamilyOf
Indicates that one entity belongs to, descends from, or is otherwise affiliated with the same clan or extended family group as another entity.
-
C.
formedByMarriageOf
Indicates that something (typically a family, union, or legal entity) comes into existence as a result of the marriage between two entities.
-
D.
spouseDynasty
chosen
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
-
E.
marriedOutsideRoyalty
Indicates that a person entered into marriage with someone who is not a member of a royal family.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e00b03c81909d04a9821907dc0d |
completed | May 2, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:10 p.m.