Triple
T28756281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikawa Bay |
E731679
|
entity |
| Predicate | locatedOnPartOfHonshu |
P93086
|
FINISHED |
| Object | central Honshu |
—
|
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: central Honshu | Statement: [Mikawa Bay, locatedOnPartOfHonshu, central Honshu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnPartOfHonshu Context triple: [Mikawa Bay, locatedOnPartOfHonshu, central Honshu]
-
A.
positionOnHonshu
chosen
Indicates that one entity is geographically located on the island of Honshu in Japan.
-
B.
locatedOnSideOfJapan
Indicates that one entity is situated on the side or coast of Japan relative to a body of water or geographic feature.
-
C.
locatedOnSideOfKyushu
Indicates that one entity is situated on a particular side or region of Kyushu.
-
D.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
-
E.
locatedInPrefectureCapitalRegion
Indicates that the subject is geographically situated within the capital region of a given prefecture.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: April 28, 2026, 6:09 a.m.