Triple
T37233449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinnōke |
E923201
|
entity |
| Predicate | typeOfHeirProvision |
P106158
|
FINISHED |
| Object | male heir only |
—
|
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: male heir only | Statement: [Shinnōke, typeOfHeirProvision, male heir only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHeirProvision Context triple: [Shinnōke, typeOfHeirProvision, male heir only]
-
A.
typeOfBequest
Indicates the specific kind or category of bequest involved in a transfer or inheritance relationship.
-
B.
typeOfProvision
Indicates the specific category or kind of provision that characterizes or qualifies a given arrangement, service, or resource.
-
C.
marriageProvision
Indicates that one party provides for, supports, or makes arrangements related to another party’s marriage (such as financial, legal, or material provisions).
-
D.
conditionOfInheritance
chosen
Indicates the legal or situational requirements that must be met for an entity to receive or transfer an inheritance.
-
E.
agreedHeir
Indicates that one entity has been formally designated and accepted as the heir of another, typically through mutual agreement or legal arrangement.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0357f9670081908a7ba1cd46a0b46a |
completed | May 12, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_6a03575e3258819093303248d1569f95 |
completed | May 12, 2026, 4:37 p.m. |
Created at: May 3, 2026, 4:15 p.m.