Triple
T38345651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shogun |
E1041531
|
entity |
| Predicate | secondMajorShogunate |
P201230
|
FINISHED |
| Object | Ashikaga shogunate |
—
|
NE NERFINISHED |
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: Ashikaga shogunate | Statement: [shogun, secondMajorShogunate, Ashikaga shogunate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondMajorShogunate Context triple: [shogun, secondMajorShogunate, Ashikaga shogunate]
-
A.
thirdMajorShogunate
Indicates that the subject is the third major shogunate in a historical sequence of shogunal governments.
-
B.
governingShogunate
Indicates that a particular shogunate holds governing authority or political control over a specified entity or region.
-
C.
shogunateName
Indicates the name assigned to a particular shogunate.
-
D.
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.
-
E.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
- F. None of above. chosen
Provenance (4 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_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_69ffdf46e18c8190a5e4f4e5211cb087 |
completed | May 10, 2026, 1:28 a.m. |
Created at: May 3, 2026, 4:30 p.m.