Triple
T32663644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pevens Way Roundabout, Broadfield, Crawley |
E835095
|
entity |
| Predicate | accessesPartOfTown |
P78464
|
FINISHED |
| Object | western side of Crawley |
—
|
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: western side of Crawley | Statement: [Pevens Way Roundabout, Broadfield, Crawley, accessesPartOfTown, western side of Crawley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesPartOfTown Context triple: [Pevens Way Roundabout, Broadfield, Crawley, accessesPartOfTown, western side of Crawley]
-
A.
accessTown
Indicates that an entity has the ability or permission to enter or make use of a particular town.
-
B.
hasAccessToTown
Indicates that one entity is permitted or able to enter, use, or otherwise access a particular town.
-
C.
accessFromCity
Indicates that there is a way to reach or enter a place starting from a specified city.
-
D.
popularAccessTown
Indicates that a town is widely used or favored as a primary access point or gateway to a surrounding area or resource.
-
E.
accessesRegion
chosen
Indicates that one entity reaches, uses, or interacts with a specific geographic or logical region.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:08 a.m.