Triple
T22323257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Assistants |
E551838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organ of a livery company |
C46098
|
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: organ of a livery company Context triple: [Court of Assistants, instanceOf, organ of a livery company]
-
A.
livery company
A livery company is a historic trade or craft guild in the City of London that evolved from regulating a profession to primarily engaging in charitable, educational, and ceremonial activities.
-
B.
component of the City of London Corporation
A component of the City of London Corporation is any organizational unit, office, committee, or functional body that operates under its authority to manage municipal governance, services, and regulatory responsibilities within the City of London.
-
C.
livery hall
A livery hall is a grand ceremonial and administrative building traditionally used as the headquarters and meeting place of a livery company or guild, especially in the City of London.
-
D.
organ of the British East India Company
An organ of the British East India Company is any official body, office, or instrument through which the Company exercised its administrative, commercial, or political functions.
-
E.
organ of the English Exchequer
An organ of the English Exchequer is an official body or administrative component within the medieval and early modern English financial system responsible for managing, auditing, or recording royal revenues and expenditures.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:42 p.m.