Triple
T6896195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hahajima |
E159375
|
entity |
| Predicate | relativeLocationToChichijima |
P16601
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Hahajima, relativeLocationToChichijima, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationToChichijima Context triple: [Hahajima, relativeLocationToChichijima, south]
-
A.
terminusOnHonshu
Indicates that the endpoint or terminus of something (such as a route, line, or connection) is located on the island of Honshu.
-
B.
relativeSizeAmongJapanMainIslands
Indicates the comparative size ranking of an island relative to the other main islands of Japan.
-
C.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
D.
relativeLocationOnIsland
chosen
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
-
E.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.