Triple
T38151049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanboku-chō period |
E952751
|
entity |
| Predicate | notableShogun |
P133643
|
FINISHED |
| Object | Ashikaga Takauji |
E957556
|
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: Ashikaga Takauji | Statement: [Nanboku-chō period, notableShogun, Ashikaga Takauji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShogun Context triple: [Nanboku-chō period, notableShogun, Ashikaga Takauji]
-
A.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
B.
hasNotableShogun
chosen
Indicates that an entity is associated with a historically notable shogun, such as by rule, leadership, or significant connection.
-
C.
notableSamurai
Indicates that the subject is recognized as a samurai of particular historical, cultural, or martial significance.
-
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.
lastShogun
Indicates that the subject is the final individual to hold the position or title of shogun in a given historical or organizational context.
- F. None of above.
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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205aa363c8190acf18e6876138b03 |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.