Triple
T32583553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenmore Dam |
E832855
|
entity |
| Predicate | nearCityLandmark |
P53174
|
FINISHED |
| Object | Heritage Park Historical Village |
—
|
NE NERFINISHED |
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: Heritage Park Historical Village | Statement: [Glenmore Dam, nearCityLandmark, Heritage Park Historical Village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearCityLandmark Context triple: [Glenmore Dam, nearCityLandmark, Heritage Park Historical Village]
-
A.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
B.
nearestCityTo
Indicates that one city is the closest in distance to a given location or entity compared to all other cities.
-
C.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
D.
proximityToLandmark
chosen
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c66c41b481908abc65d5d284bcee |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.