Triple
T31331639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ninoshima |
E799046
|
entity |
| Predicate | distanceToHiroshima |
P150838
|
FINISHED |
| Object | about 4 kilometers 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: about 4 kilometers south | Statement: [Ninoshima, distanceToHiroshima, about 4 kilometers south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHiroshima Context triple: [Ninoshima, distanceToHiroshima, about 4 kilometers south]
-
A.
distanceFromHiroshimaCityCenter
chosen
Indicates the measured distance between a given location and the central point of Hiroshima City.
-
B.
distanceFromHiroshimaStation
Indicates the measured distance between a given place and Hiroshima Station.
-
C.
yieldComparedToHiroshima
Indicates the explosive yield of something expressed in comparison to the yield of the Hiroshima atomic bomb.
-
D.
distanceFromFukushimaDaiichi_km
Indicates the distance, measured in kilometers, between an entity and the Fukushima Daiichi nuclear power plant.
-
E.
distanceFromChernobylTown
Indicates the spatial distance between an entity and the town of Chernobyl.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01bdacb52481909c56b0398106640e |
completed | May 11, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a01bd30c8ec8190b1e54d7658b01a8d |
completed | May 11, 2026, 11:27 a.m. |
Created at: April 29, 2026, 9:16 p.m.