Triple
T11538409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Counsel |
E273606
|
entity |
| Predicate | mayBeAppointedFrom |
P21016
|
FINISHED |
| Object | private bar |
—
|
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: private bar | Statement: [Queen's Counsel, mayBeAppointedFrom, private bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAppointedFrom Context triple: [Queen's Counsel, mayBeAppointedFrom, private bar]
-
A.
appointedFrom
chosen
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
B.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
C.
mayBeConferredAs
Indicates that something has the potential or authorization to be formally granted or bestowed upon an entity under certain conditions.
-
D.
canBeChairOf
Indicates that an entity has the eligibility or capacity to serve as the chair (leader) of a specified group, committee, or organization.
-
E.
appointedBy
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8839cdf688190ae75c0e6fece8e33 |
completed | April 10, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.