Triple
T36450600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takeda clan |
E897996
|
entity |
| Predicate | originatedAsBranchOf |
P118109
|
FINISHED |
| Object | Kai Minamoto clan |
E186146
|
NE 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: Kai Minamoto clan | Statement: [Takeda clan, originatedAsBranchOf, Kai Minamoto clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedAsBranchOf Context triple: [Takeda clan, originatedAsBranchOf, Kai Minamoto clan]
-
A.
establishedAsBranchBy
chosen
Indicates that one entity was created or designated as a branch or subsidiary by another entity.
-
B.
openedAsBranchOf
Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
-
C.
branchOrigin
Indicates that one entity is the source or starting point from which another entity branches or diverges.
-
D.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
E.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or organization.
- F. None of above.
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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7c81ff48190bc133d93b9d97087 |
completed | June 28, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.