Triple
T33941331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genryaku |
E870172
|
entity |
| Predicate | associatedShogunateRise |
P206742
|
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: [Genryaku, associatedShogunateRise, Kamakura shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShogunateRise Context triple: [Genryaku, associatedShogunateRise, Kamakura shogunate]
-
A.
shogunateName
Indicates the name assigned to a particular shogunate.
-
B.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
C.
servedShogun
Indicates that one entity was in a position of service, allegiance, or duty to a shogun.
-
D.
statusOfShogunate
Indicates the political or operational condition or state of a shogunate at a given time.
-
E.
shōgun
Indicates that an entity holds the role or title of shōgun in relation to another entity, typically as its military ruler or supreme commander.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36a01c57ac819093ac5d088894cd06 |
completed | June 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:49 a.m.