Triple
T38345650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shogun |
E1041531
|
entity |
| Predicate | firstMajorShogunate |
P204610
|
FINISHED |
| Object | Kamakura shogunate |
E91830
|
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: Kamakura shogunate | Statement: [shogun, firstMajorShogunate, Kamakura shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMajorShogunate Context triple: [shogun, firstMajorShogunate, Kamakura shogunate]
-
A.
thirdMajorShogunate
Indicates that the subject is the third major shogunate in a historical sequence of shogunal governments.
-
B.
secondMajorShogunate
Indicates that an entity served as the second major shogunate in a historical or political sequence of shogunal governments.
-
C.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
D.
shogunateName
Indicates the name assigned to a particular shogunate.
-
E.
firstDaimyo
Indicates that the subject is the first (initial or founding) daimyō associated with the specified domain, lineage, or context.
- F. None of above. chosen
Provenance (5 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41b29695a881908979ddf2622785ce |
completed | June 28, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:30 p.m.