Triple
T7987960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Helena City Park |
E185729
|
entity |
| Predicate | isUrbanProximity |
P44123
|
FINISHED |
| Object | adjacent to downtown Helena |
—
|
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: adjacent to downtown Helena | Statement: [Mount Helena City Park, isUrbanProximity, adjacent to downtown Helena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanProximity Context triple: [Mount Helena City Park, isUrbanProximity, adjacent to downtown Helena]
-
A.
hasUrbanProximity
chosen
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
B.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
C.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
D.
hasUrbanAreaApprox
Indicates an approximate measure or estimate of the size or extent of an entity’s urban area.
-
E.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4d11b08190aa13afb17155462c |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb048009a08190b4c577208a9f8f76 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:15 p.m.