Triple
T22684034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sōya Misaki |
E560860
|
entity |
| Predicate | distanceToSakhalinApprox |
P149235
|
FINISHED |
| Object | about 43 kilometers |
—
|
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 43 kilometers | Statement: [Sōya Misaki, distanceToSakhalinApprox, about 43 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSakhalinApprox Context triple: [Sōya Misaki, distanceToSakhalinApprox, about 43 kilometers]
-
A.
distanceToPetropavlovskKamchatsky
Indicates the spatial distance between an entity and the location of Petropavlovsk-Kamchatsky.
-
B.
distanceToVladivostok_km
Indicates the physical distance, measured in kilometers, between a given location and Vladivostok.
-
C.
distanceToKoreanPeninsula
Indicates the measured or estimated spatial distance between a given entity or location and the Korean Peninsula.
-
D.
distanceToYamalPeninsula
Indicates the measured or calculated distance between a given entity’s location and the Yamal Peninsula.
-
E.
distanceToArkhangelskApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17862c8a48190912a8ad09dfda795 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.