Triple
T16107582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Aizu |
E390778
|
entity |
| Predicate | modernPrefecture |
P39977
|
FINISHED |
| Object | Fukushima Prefecture |
—
|
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: Fukushima Prefecture | Statement: [Battle of Aizu, modernPrefecture, Fukushima Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernPrefecture Context triple: [Battle of Aizu, modernPrefecture, Fukushima Prefecture]
-
A.
prefectureOfHeadquarters
Indicates the administrative prefecture in which an organization's headquarters is located.
-
B.
都道府県
chosen
Indicates a relationship where an entity is a Japanese prefecture or belongs to/pertains to a specific Japanese prefecture.
-
C.
prefectureCapitalRegion
Indicates that a region serves as the capital administrative area within a prefecture.
-
D.
hasPrefecturalOffice
Indicates that a given location or administrative unit contains or hosts an official prefectural government office.
-
E.
hasPrefecture
Indicates that one administrative region or country possesses or is associated with a specific prefecture as a subordinate territorial unit.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6e55c08190b77f344e4e8c42ad |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.