Triple
T25660138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Heights, Minnesota |
E643353
|
entity |
| Predicate | distanceToDowntownMinneapolis |
P27979
|
FINISHED |
| Object | approximately 5 miles |
—
|
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 5 miles | Statement: [Columbia Heights, Minnesota, distanceToDowntownMinneapolis, approximately 5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDowntownMinneapolis Context triple: [Columbia Heights, Minnesota, distanceToDowntownMinneapolis, approximately 5 miles]
-
A.
distanceToMinneapolis
chosen
Indicates the measured distance between a given entity’s location and the city of Minneapolis.
-
B.
distanceFromDowntown
Indicates the physical distance between a given location and the central downtown area.
-
C.
distanceToSaintPaul
Indicates the measured spatial distance between a given entity and the location of Saint Paul.
-
D.
distanceFromDesMoines
Indicates the physical distance between a given location and the city of Des Moines.
-
E.
distance to Midtown Manhattan (miles)
Indicates the physical separation between a location and Midtown Manhattan, measured in miles.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 21, 2026, 6:51 p.m.