Triple
T36102599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobayakawa Takakage |
E1044254
|
entity |
| Predicate | adoptedFromClan |
P91408
|
FINISHED |
| Object | Kobayakawa 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: Kobayakawa clan | Statement: [Kobayakawa Takakage, adoptedFromClan, Kobayakawa clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedFromClan Context triple: [Kobayakawa Takakage, adoptedFromClan, Kobayakawa clan]
-
A.
adoptedFrom
chosen
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
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.
formerRulingClan
Indicates that a clan previously held ruling power or authority over a group, territory, or polity but no longer does so.
-
D.
fatherClan
Indicates a kinship relationship where one entity belongs to, descends from, or is affiliated with the clan of the father of another entity.
-
E.
adoptedByFamilyOf
Indicates that an entity has been taken in and legally or formally accepted as a member by another entity’s 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.