Triple
T32775627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herring Cove Road |
E838194
|
entity |
| Predicate | hasAdjacentFacilityType |
P5648
|
FINISHED |
| Object | retail stores |
—
|
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: retail stores | Statement: [Herring Cove Road, hasAdjacentFacilityType, retail stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentFacilityType Context triple: [Herring Cove Road, hasAdjacentFacilityType, retail stores]
-
A.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
-
B.
hasNearbySiteType
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
-
C.
hasSiblingFacility
Indicates that one facility is related to another as a sibling facility, typically sharing a common parent organization or similar hierarchical level.
-
D.
hasNearbyFacility
chosen
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
E.
adjacentFacilitySecurityClass
Indicates that two facilities located next to each other share a specified level or classification of security.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:13 a.m.