Triple
T33039617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southampton Row |
E845421
|
entity |
| Predicate | hasNearbyParkOrSquare |
P33602
|
FINISHED |
| Object | Russell Square gardens |
—
|
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: Russell Square gardens | Statement: [Southampton Row, hasNearbyParkOrSquare, Russell Square gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyParkOrSquare Context triple: [Southampton Row, hasNearbyParkOrSquare, Russell Square gardens]
-
A.
hasNearbyParkFeature
Indicates that one place or object is located close to a park-related feature, such as a park, playground, or green space.
-
B.
hasNearbyParkEntrance
Indicates that one location is situated close to an entrance of a park.
-
C.
isNeighborhoodParkOf
Indicates that a park is located within and serves as a local recreational area for a specific neighborhood.
-
D.
hasNearbyGreenSpace
chosen
Indicates that an entity is located close to an area of green space, such as a park, garden, or natural vegetation.
-
E.
hasParkingNearby
Indicates that a location has one or more parking facilities or spaces available within a close surrounding area.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 1, 2026, 1:24 a.m.