Triple
T27818722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montana |
E702752
|
entity |
| Predicate | borderLengthWithCanada |
P26571
|
FINISHED |
| Object | long land border |
—
|
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: long land border | Statement: [Montana, borderLengthWithCanada, long land border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderLengthWithCanada Context triple: [Montana, borderLengthWithCanada, long land border]
-
A.
hasBorderLengthWithCanada_km
chosen
Indicates the length, in kilometers, of the land or maritime border that an entity shares with Canada.
-
B.
hasBorderLengthWithUSA
Indicates that the length of the land or maritime border shared between a given country or region and the USA has a specified measurement.
-
C.
distanceToCanadianBorder
Indicates the measured or estimated spatial distance between a given location and the nearest point on the Canadian national border.
-
D.
borderLengthWithFinland
Indicates the total length of the land or maritime border that an entity shares with Finland.
-
E.
hasBorderTownOnCanadianSide
Indicates that one location has a corresponding border town situated on the Canadian side of an international boundary.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 5:47 p.m.