Triple
T3406452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsushima Island |
E71783
|
entity |
| Predicate | distanceToKyushu |
P49110
|
FINISHED |
| Object | approximately 50 km |
—
|
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: approximately 50 km | Statement: [Tsushima Island, distanceToKyushu, approximately 50 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKyushu Context triple: [Tsushima Island, distanceToKyushu, approximately 50 km]
-
A.
distanceFromKyoto
Indicates the measured spatial distance between a given entity’s location and the city of Kyoto.
-
B.
distanceFromKyotoStation
Indicates the spatial distance between a given location and Kyoto Station.
-
C.
distanceFromTokyo
Indicates the physical distance between a given location and Tokyo.
-
D.
distanceFromOsaka
Indicates the measured distance between a given place or object and the city of Osaka.
-
E.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8ec68c88190913df5f6cafad9e9 |
completed | March 8, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb21a437c81908bca88d5e123d744 |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.