Triple
T11309969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kuni no miyatsuko |
E267811
|
entity |
| Predicate | inheritedAs |
P1920
|
FINISHED |
| Object | hereditary title |
—
|
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: hereditary title | Statement: [kuni no miyatsuko, inheritedAs, hereditary title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritedAs Context triple: [kuni no miyatsuko, inheritedAs, hereditary title]
-
A.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
B.
losesInheritanceThrough
Indicates that one party forfeits or is disqualified from receiving an inheritance as a consequence of another specified party or condition.
-
C.
inheritanceStatus
Indicates the type or condition of inheritance rights or succession status that applies between related parties.
-
D.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
E.
typeOfInheritance
chosen
Indicates the kind or pattern of inheritance by which a trait, property, or characteristic is passed from one entity or generation to another.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c0b3b88190ac0e3d6a5ad3b9bc |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.