Triple
T23952747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haberdashers' Company |
E603092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Great Twelve Livery Company |
C18978
|
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: Great Twelve Livery Company Context triple: [Haberdashers' Company, instanceOf, Great Twelve Livery Company]
-
A.
livery company
chosen
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.
organ of a livery company
An organ of a livery company is a formal body or office within the company’s governance structure, such as a court, committee, or officer role, that carries out specific administrative, regulatory, or ceremonial functions.
-
C.
senior officer of a livery company
A senior officer of a livery company is a high-ranking elected or appointed member responsible for leading the company’s governance, representing it in civic and ceremonial functions, and overseeing its charitable, educational, and professional activities.
-
D.
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.
-
E.
royal chartered company
A royal chartered company is a business organization established and granted special rights, privileges, and legal status by a monarch through a formal charter, often to conduct trade or colonization.
- F. None of above.
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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:20 p.m.