Triple
T38101958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kujō Takeko |
E951405
|
entity |
| Predicate | hasFamilyRank |
P128155
|
FINISHED |
| Object | high court nobility |
—
|
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: high court nobility | Statement: [Kujō Takeko, hasFamilyRank, high court nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyRank Context triple: [Kujō Takeko, hasFamilyRank, high court nobility]
-
A.
familyRank
chosen
Indicates the hierarchical position or status an entity holds within a family or kinship structure.
-
B.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
C.
hasFamilyHead
Indicates that one entity serves as the primary head or leader of another entity’s family unit.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
hasFamilyOrganization
Indicates that an entity is associated with, belongs to, or is structured within a particular family-based organizational unit or system.
- 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 3, 2026, 4:21 p.m.