Triple
T28105252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir John Soane family tomb |
E710343
|
entity |
| Predicate | situatedInCemetery |
P3802
|
FINISHED |
| Object | St Pancras 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: St Pancras Gardens | Statement: [Sir John Soane family tomb, situatedInCemetery, St Pancras Gardens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInCemetery Context triple: [Sir John Soane family tomb, situatedInCemetery, St Pancras Gardens]
-
A.
locatedInCemetery
chosen
Indicates that one entity is situated within the grounds or area of a cemetery.
-
B.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
C.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
D.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
E.
hasNearbyCemetery
Indicates that one entity is located close to, or in the immediate vicinity of, a cemetery associated with another 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 9:07 p.m.