Triple
T27134453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaka family |
E681642
|
entity |
| Predicate | heldPrincelyStatusIn |
P73847
|
FINISHED |
| Object | modern era |
—
|
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: modern era | Statement: [Asaka family, heldPrincelyStatusIn, modern era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldPrincelyStatusIn Context triple: [Asaka family, heldPrincelyStatusIn, modern era]
-
A.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
-
B.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
C.
aristocraticTitleHeldTo
chosen
Indicates that one entity holds or bears an aristocratic or noble title in relation to another entity (such as a person, family, or jurisdiction).
-
D.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
E.
aristocraticTitleHeldBy
Indicates that a specific aristocratic or noble title is held or borne by a particular person.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 9:06 a.m.