Triple
T21128788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ajos harbour |
E520627
|
entity |
| Predicate | distanceToKemiCityCentre |
P142954
|
FINISHED |
| Object | approximately 10–15 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 10–15 km | Statement: [Ajos harbour, distanceToKemiCityCentre, approximately 10–15 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKemiCityCentre Context triple: [Ajos harbour, distanceToKemiCityCentre, approximately 10–15 km]
-
A.
distanceFromNagoyaCityCenterKilometers
Indicates the distance, measured in kilometers, between an entity and the center of Nagoya City.
-
B.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
C.
distanceFromŌmiyaStation_km
Indicates the distance, measured in kilometers, between a given place and Ōmiya Station.
-
D.
distanceToSapporo
Indicates the measured or calculated distance between a given entity and the location of Sapporo.
-
E.
distanceFromKyotoStation
Indicates the spatial distance between a given location and Kyoto Station.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7223b4c4c8190b9fffa610588651e |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:56 p.m.