Triple
T38702980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kujō Asako |
E950188
|
entity |
| Predicate | partOfNobleLineage |
P143401
|
FINISHED |
| Object | Five Regent Houses |
E950185
|
NE 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: Five Regent Houses | Statement: [Kujō Asako, partOfNobleLineage, Five Regent Houses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfNobleLineage Context triple: [Kujō Asako, partOfNobleLineage, Five Regent Houses]
-
A.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
B.
hasNobleHouseOrigin
chosen
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
C.
aristocraticOrigin
Indicates that an entity originates from, or is derived from, an aristocratic or noble background.
-
D.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
-
E.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
- F. None of above.
Provenance (4 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01f4d954e08190aff3756955212d67 |
completed | May 11, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a420e0889e4819098b40228702d3148 |
completed | June 29, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_6a01edadb9248190be592287530740a5 |
completed | May 11, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:33 p.m.