Triple
T14579892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariake Sea |
E342161
|
entity |
| Predicate | locatedOnSideOfKyushu |
P114936
|
FINISHED |
| Object | western side of Kyushu |
—
|
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: western side of Kyushu | Statement: [Ariake Sea, locatedOnSideOfKyushu, western side of Kyushu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfKyushu Context triple: [Ariake Sea, locatedOnSideOfKyushu, western side of Kyushu]
-
A.
positionOnHonshu
Indicates that one entity is geographically located on the island of Honshu in Japan.
-
B.
locatedInRegionOfIsland
Indicates that an entity is situated within a specific region that is part of an island.
-
C.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
-
D.
locatedInRegionOfPrefecture
Indicates that one entity is geographically situated within a specific region that belongs to or is administered as part of a given prefecture.
-
E.
locatedInHeadTemplePrefecture
Indicates that something is situated within the prefecture where the head temple of a religious organization is located.
- F. None of above. chosen
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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.