Triple
T15901142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Toba–Fushimi |
E385590
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Fushimi |
—
|
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: Fushimi | Statement: [Battle of Toba–Fushimi, location, Fushimi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fushimi Context triple: [Battle of Toba–Fushimi, location, Fushimi]
-
A.
Fushimi
chosen
Fushimi is a historic district in Kyoto, Japan, known for its castle and its association with key events and figures of the late Sengoku period.
-
B.
Fushimi
Fushimi is a central commercial and business district in Nagoya, Japan, known for its offices, shopping, dining, and cultural attractions.
-
C.
Komagome
Komagome is a residential and commercial neighborhood in Tokyo known for its traditional atmosphere, historic temples, and the renowned Rikugien Garden.
-
D.
Toyonaka
Toyonaka is a suburban city in Japan’s Kansai region known for its residential neighborhoods, educational institutions, and proximity to central Osaka.
-
E.
Ueno
Ueno is a major district in Tokyo known for Ueno Park, its museums, zoo, and busy transportation hub.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563db01081908dd94a2536ef2107 |
completed | April 16, 2026, 9:35 p.m. |
Created at: April 10, 2026, 4:51 a.m.