Triple
T16406162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōjō Masako |
E398436
|
entity |
| Predicate | child |
P120
|
FINISHED |
| Object | Ōhime |
E446383
|
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: Ōhime | Statement: [Hōjō Masako, child, Ōhime]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ōhime Context triple: [Hōjō Masako, child, Ōhime]
-
A.
Ōhime
chosen
Ōhime was the eldest daughter of Minamoto no Yoritomo, the first shogun of the Kamakura shogunate, and his wife Hōjō Masako, living during Japan’s late 12th century.
-
B.
Otohime
Otohime is a figure from Japanese legend associated with the warrior Minamoto no Yoshitsune, sometimes depicted as his daughter in later literary and folkloric traditions.
-
C.
Yoriko
Yoriko is a Japanese feminine given name commonly borne by women and girls in Japan.
-
D.
Yuzuriha
Yuzuriha is an evergreen tree commonly used in Japan as a symbolic plant, notably serving as the official tree emblem of Kōchi Prefecture.
-
E.
Takako
Takako is a Japanese feminine given name borne by various notable figures in politics, arts, and entertainment.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d2b4e48190b7153f198639e9cd |
completed | April 18, 2026, 6:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c62614c8190acd6d211cab1be11 |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:09 a.m.