Triple
T24527576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsudaira clan |
E606708
|
entity |
| Predicate | ancestralHouseOf |
P132162
|
FINISHED |
| Object | Tokugawa Ieyasu |
—
|
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: Tokugawa Ieyasu | Statement: [Matsudaira clan, ancestralHouseOf, Tokugawa Ieyasu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ancestralHouseOf Context triple: [Matsudaira clan, ancestralHouseOf, Tokugawa Ieyasu]
-
A.
ancestorHouse
Indicates that one entity is the house or dwelling associated with the ancestors of another entity.
-
B.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
C.
patriarchResidence
Indicates that a person serves as the primary male head or patriarch within a particular residence or household.
-
D.
builtResidence
Indicates that one entity constructed or was responsible for constructing a residence for another entity or for itself.
-
E.
foundingHouse
chosen
Indicates that one entity is the original ruling family, dynasty, or lineage that established or founded another entity (such as a state, organization, or institution).
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.