Triple
T37233442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinnōke |
E923201
|
entity |
| Predicate | successionRightType |
P71549
|
FINISHED |
| Object | collateral succession |
—
|
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: collateral succession | Statement: [Shinnōke, successionRightType, collateral succession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionRightType Context triple: [Shinnōke, successionRightType, collateral succession]
-
A.
successionRight
Indicates the legal or customary entitlement of one entity to inherit, assume, or take over the position, property, or role of another.
-
B.
successionBasis
chosen
Indicates the legal or customary basis on which one entity succeeds or takes over from another in a position, role, or title.
-
C.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
-
D.
typeOfSuccessionRank
Indicates the specific kind or category of succession ranking that applies within a succession order or hierarchy.
-
E.
recognizesSuccessionRightTo
Indicates that one party formally acknowledges another party’s legitimate claim or entitlement to inherit a position, title, or property.
- 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_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 3, 2026, 4:15 p.m.