Triple
T28842888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannons |
E728368
|
entity |
| Predicate | successorEstateOnSite |
P11081
|
FINISHED |
| Object | Little Stanmore House |
—
|
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: Little Stanmore House | Statement: [Cannons, successorEstateOnSite, Little Stanmore House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEstateOnSite Context triple: [Cannons, successorEstateOnSite, Little Stanmore House]
-
A.
successorSite
Indicates that one site directly follows and replaces another site in a sequence or evolution of sites.
-
B.
successorBuildingOnSite
chosen
Indicates that one building directly replaces another on the same physical site or location.
-
C.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
D.
successorStateSite
Indicates that one site or state of a site directly follows another as its immediate successor in a sequence or process.
-
E.
laterFunctionOfEstate
Indicates that one function or role of an estate occurs at a later time or stage relative to another function of that same estate.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 28, 2026, 6:41 a.m.