Triple
T25786920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Warden |
E649443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | position in a livery company |
C22167
|
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: position in a livery company Context triple: [Prime Warden, instanceOf, position in a livery company]
-
A.
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.
-
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.
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.
-
D.
position in a professional association
chosen
A position in a professional association represents a formally recognized role or office held by a member, defined by specific responsibilities, authority, and term within the association’s organizational structure.
-
E.
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.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:55 a.m.