Triple
T28383899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swain’s Lane entrance of Highgate Cemetery East |
E718963
|
entity |
| Predicate | proximityToKarlMarxMemorial |
P53174
|
FINISHED |
| Object | close |
—
|
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: close | Statement: [Swain’s Lane entrance of Highgate Cemetery East, proximityToKarlMarxMemorial, close]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToKarlMarxMemorial Context triple: [Swain’s Lane entrance of Highgate Cemetery East, proximityToKarlMarxMemorial, close]
-
A.
proximityToLandmark
chosen
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
B.
distanceFromFord’sTheatre
Indicates the spatial distance between an entity and Ford’s Theatre.
-
C.
distanceToOświęcim
Indicates the physical distance between a given entity and the location Oświęcim.
-
D.
commemoratesNearby
Indicates that one entity serves to honor or memorialize something located in close physical proximity to it.
-
E.
hasNearbyMemorials
Indicates that one or more memorials are located in close physical proximity to the referenced entity.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cb90ba88190b2dd6a4a888816f4 |
completed | May 2, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:08 a.m.