Triple
T18535732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayswater Road |
E452960
|
entity |
| Predicate | hasNearbyParkEntrance |
P132043
|
FINISHED |
| Object | Hyde Park entrances |
—
|
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: Hyde Park entrances | Statement: [Bayswater Road, hasNearbyParkEntrance, Hyde Park entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyParkEntrance Context triple: [Bayswater Road, hasNearbyParkEntrance, Hyde Park entrances]
-
A.
hasParkingNearby
Indicates that a location has one or more parking facilities or spaces available within a close surrounding area.
-
B.
hasNearbyUndergroundStationEntrance
Indicates that one entity is located close to an entrance of an underground (subway/metro) station.
-
C.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
D.
hasOpenSpaceNearby
Indicates that an entity is located near or adjacent to an area that is open, unobstructed, or undeveloped.
-
E.
nearestNationalParkEntrance
Indicates the relationship where a given location is associated with the closest entrance point of a national park.
- F. None of above. chosen
Provenance (4 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5340193588190ace2c09c6a94cf81 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.