Triple
T24479475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Cemetery |
E617327
|
entity |
| Predicate | hasParentSite |
P5003
|
FINISHED |
| Object | Brookwood Cemetery |
—
|
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: Brookwood Cemetery | Statement: [South Cemetery, hasParentSite, Brookwood Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentSite Context triple: [South Cemetery, hasParentSite, Brookwood Cemetery]
-
A.
hasMainSite
Indicates that one entity is designated as the primary or central site associated with another entity.
-
B.
containsSite
chosen
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
D.
hasSisterSite
Indicates that one site is formally associated with another as a sister site, typically implying a parallel or closely related counterpart.
-
E.
hasParentSystem
Indicates that one system is hierarchically contained within or derived from another, which serves as its parent system.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed509c88190a0071f8e78b38887 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.