Triple
T37065846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amesbury Community Area |
E917440
|
entity |
| Predicate | hasNeighbouringCommunityArea |
P4647
|
FINISHED |
| Object | Salisbury Community Area |
—
|
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: Salisbury Community Area | Statement: [Amesbury Community Area, hasNeighbouringCommunityArea, Salisbury Community Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringCommunityArea Context triple: [Amesbury Community Area, hasNeighbouringCommunityArea, Salisbury Community Area]
-
A.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
-
B.
hasNearbyCommunity
chosen
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
C.
hasNeighbouringLocality
Indicates that one locality is geographically adjacent to or directly borders another locality.
-
D.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
-
E.
hasCommunityDistrict
Indicates that an entity is located within, associated with, or falls under the jurisdiction of a specific community district.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: May 3, 2026, 4:14 p.m.