Triple
T20809550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moosonee |
E512260
|
entity |
| Predicate | distanceToNearestRoadNetwork_km |
P117786
|
FINISHED |
| Object | about 150 |
—
|
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 150 | Statement: [Moosonee, distanceToNearestRoadNetwork_km, about 150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNearestRoadNetwork_km Context triple: [Moosonee, distanceToNearestRoadNetwork_km, about 150]
-
A.
distanceFromRoads
chosen
Indicates the measured or estimated spatial distance between a location and the nearest road.
-
B.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
C.
distanceToNomeByRoad
Indicates the road travel distance between a given place and the city of Nome.
-
D.
trekDistanceFromRoadHead
Indicates the distance one must trek from the road head (road access point) to reach a specified location.
-
E.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2d199888190b8b190c928f510b7 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:40 p.m.