Triple
T4294791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater London Council (in respect of residual functions) |
E99684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | successor administrative arrangement |
C15545
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: successor administrative arrangement Context triple: [Greater London Council (in respect of residual functions), instanceOf, successor administrative arrangement]
-
A.
succession office
A succession office is an administrative entity responsible for managing, documenting, and legally processing the transfer of rights, titles, or property from one holder to another, typically after death or organizational change.
-
B.
successor state
A successor state is a new system configuration that directly results from applying a specific action or transition to a current state within a defined process or model.
-
C.
succession law
Succession law is the body of legal rules and principles that govern how a deceased person's property, rights, and obligations are transferred to heirs and beneficiaries.
-
D.
succession settlement
A succession settlement is a legal arrangement that determines how a person's estate, titles, or rights are to be transferred and distributed among heirs or beneficiaries after their death.
-
E.
act of succession
An act of succession is a formal event or process by which authority, title, or position is transferred from one holder to another, establishing a new legitimate bearer.
- F. None of above. chosen
Provenance (1 batch)
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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:08 p.m.