Triple
T37403149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Mayor’s Consort |
E929054
|
entity |
| Predicate | nonExecutive |
P23628
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [Lord Mayor’s Consort, nonExecutive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonExecutive Context triple: [Lord Mayor’s Consort, nonExecutive, true]
-
A.
isNonExecutive
chosen
Indicates that an entity holds a role or position that does not involve executive or top-level managerial authority within an organization.
-
B.
nonClerical
Indicates that an entity, role, or activity is not related to clerical or administrative work or duties.
-
C.
nonExecutiveMembersAppointedOnAdviceOf
Indicates that the appointment of non-executive members is made based on the formal recommendation or advice of a specified person or body.
-
D.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
-
E.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.