Triple
T4240179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rusutsu |
E95392
|
entity |
| Predicate | distanceFromSapporo |
P49917
|
FINISHED |
| Object | approximately 70 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: approximately 70 kilometers | Statement: [Rusutsu, distanceFromSapporo, approximately 70 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSapporo Context triple: [Rusutsu, distanceFromSapporo, approximately 70 kilometers]
-
A.
distanceToSapporo
chosen
Indicates the measured or calculated distance between a given entity and the location of Sapporo.
-
B.
distanceFromTokyo
Indicates the physical distance between a given location and Tokyo.
-
C.
distanceToKyushu
Indicates the spatial distance between a given entity’s location and the region of Kyushu.
-
D.
distanceFromOsaka
Indicates the measured distance between a given place or object and the city of Osaka.
-
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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e77fb5c8190b298818acb68ff63 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.