Triple
T25785194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grove Hill (local toponym) |
E649398
|
entity |
| Predicate | spatiallyOverlaps |
P1867
|
FINISHED |
| Object | area around Grove Hill Memorial Park |
—
|
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: area around Grove Hill Memorial Park | Statement: [Grove Hill (local toponym), spatiallyOverlaps, area around Grove Hill Memorial Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spatiallyOverlaps Context triple: [Grove Hill (local toponym), spatiallyOverlaps, area around Grove Hill Memorial Park]
-
A.
overlapsWith
chosen
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
B.
spatialRelation
Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
-
C.
regionContains
Indicates that one region spatially encompasses or includes another region within its boundaries.
-
D.
geographicOverlap
Indicates that two geographic areas share at least part of the same physical space or territory.
-
E.
supportsSpatialQueries
Indicates that the subject system or component is capable of performing spatial (location- or geometry-based) queries on data.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fefa2c908190939ca0f6f68420ad |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:54 a.m.