Triple
T20919770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omuta |
E515173
|
entity |
| Predicate | distanceToPrefecturalCapitalApproxKm |
P139399
|
FINISHED |
| Object | 60-70 |
—
|
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: 60-70 | Statement: [Omuta, distanceToPrefecturalCapitalApproxKm, 60-70]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPrefecturalCapitalApproxKm Context triple: [Omuta, distanceToPrefecturalCapitalApproxKm, 60-70]
-
A.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
-
B.
prefecturalCapitalDistanceRelation
chosen
Indicates a spatial relationship specifying the distance between an entity and the capital city of its prefecture.
-
C.
prefectureCapitalNearby
Indicates that a prefecture’s capital city is geographically close to the referenced location.
-
D.
distanceToProvinceCapital_km
Indicates the distance, measured in kilometers, between a given location and the capital city of its province.
-
E.
distanceFromRegionalCapital
Indicates the measured spatial distance between a given place and its corresponding regional capital.
- 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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6ec66593c819091ecf0c553e0aead |
completed | April 21, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:48 p.m.