Triple
T16206781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmu |
E393347
|
entity |
| Predicate | capitalRelocationYearToHeian-kyō |
P67016
|
FINISHED |
| Object | 794 |
—
|
LITERAL 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: 794 | Statement: [Kanmu, capitalRelocationYearToHeian-kyō, 794]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRelocationYearToHeian-kyō Context triple: [Kanmu, capitalRelocationYearToHeian-kyō, 794]
-
A.
relocatedToNaraInYear
Indicates that an entity moved its location to Nara in the specified year.
-
B.
movedImperialCapitalFrom
Indicates the action of transferring an imperial capital city from one location to another.
-
C.
movedImperialCapitalTo
chosen
Indicates that a ruler or governing authority relocated the primary seat of imperial government from one capital city to another.
-
D.
reunifiedAsCapitalInYear
Indicates that an entity regained its status as a capital city in a specified year after a period of not holding that status.
-
E.
movedImperialResidenceYear
Indicates the year in which an imperial residence was relocated from one place to another.
- F. None of above.
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227101a3c819095ef40e50bf66433 |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.