Triple
T8882650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kapuskasing |
E211446
|
entity |
| Predicate | distanceFromTimmins |
P85511
|
FINISHED |
| Object | approximately 160 km northwest |
—
|
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 160 km northwest | Statement: [Kapuskasing, distanceFromTimmins, approximately 160 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTimmins Context triple: [Kapuskasing, distanceFromTimmins, approximately 160 km northwest]
-
A.
distanceFromFortWilliam
Indicates the measured distance between an entity and Fort William.
-
B.
distanceFromCalgary
Indicates the spatial distance between a given location and the city of Calgary.
-
C.
distanceFromToronto
Indicates the spatial distance between a given entity and the location of Toronto.
-
D.
distanceToEdmonton
Indicates the spatial distance between a given entity’s location and the city of Edmonton.
-
E.
distanceToWinnipeg
Indicates the spatial distance between a given entity’s location and the city of Winnipeg.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616a01f48190b8bbde0e898a38c7 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:53 p.m.