Triple
T19262316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuni-no-miya house |
E481677
|
entity |
| Predicate | roleInImperialFamily |
P25666
|
FINISHED |
| Object | provided consorts to reigning emperors |
—
|
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: provided consorts to reigning emperors | Statement: [Kuni-no-miya house, roleInImperialFamily, provided consorts to reigning emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInImperialFamily Context triple: [Kuni-no-miya house, roleInImperialFamily, provided consorts to reigning emperors]
-
A.
generationWithinImperialFamily
Indicates the ordinal generation level of an individual within an imperial family lineage (e.g., first generation, second generation).
-
B.
hadMemberInImperialFamily
Indicates that an entity had at least one member belonging to an imperial family.
-
C.
familyRelationToEmperor
Indicates that one entity is related to an emperor by family ties, specifying a kinship or familial connection between them.
-
D.
dynasticRole
chosen
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
E.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb8a022c8190b313e9d11d38e482 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.