Triple
T26306571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogasawara, Tokyo |
E661700
|
entity |
| Predicate | distanceFromTokyoMainland |
P25290
|
FINISHED |
| Object | about 1000 km south of central Tokyo |
—
|
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 1000 km south of central Tokyo | Statement: [Ogasawara, Tokyo, distanceFromTokyoMainland, about 1000 km south of central Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTokyoMainland Context triple: [Ogasawara, Tokyo, distanceFromTokyoMainland, about 1000 km south of central Tokyo]
-
A.
distanceFromTokyo
chosen
Indicates the physical distance between a given location and Tokyo.
-
B.
distanceToSapporo
Indicates the measured or calculated distance between a given entity and the location of Sapporo.
-
C.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
D.
locatedInDirectionFromTokyo
Indicates that one place is situated in a specified compass direction relative to Tokyo.
-
E.
distanceFromKyoto
Indicates the measured spatial distance between a given entity’s location and the city of Kyoto.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 26, 2026, 10:19 p.m.