Triple
T16332269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōjō Tokimasa |
E396583
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hōjō |
E1063023
|
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: Hōjō | Statement: [Hōjō Tokimasa, familyName, Hōjō]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hōjō Context triple: [Hōjō Tokimasa, familyName, Hōjō]
-
A.
Hōjō
chosen
Hōjō was a powerful samurai clan that rose to prominence as feudal lords in Japan during the late Sengoku and early Edo periods.
-
B.
Hōjō Ujitsuna
Hōjō Ujitsuna was a prominent Sengoku-period daimyō who expanded and consolidated the power of the Later Hōjō clan in the Kantō region of Japan.
-
C.
Hōjō Sōun
Hōjō Sōun was a prominent early Sengoku-period daimyō who founded the Later Hōjō clan and established its power base in the Kantō region of Japan.
-
D.
Hōjō Tokimasa
Hōjō Tokimasa was the first shikken (regent) of the Kamakura shogunate and the founding leader of the Hōjō clan’s political dominance in medieval Japan.
-
E.
Hōjō Yasutoki
Hōjō Yasutoki was a prominent early 13th-century Japanese military ruler and statesman who strengthened the Kamakura shogunate’s legal and administrative systems as its de facto leader.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e0b1388190824b286e8452fb32 |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007d9a8d7481908c7bc4711ddacc13 |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:07 a.m.