Triple
T10613799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law Commission |
E276068
|
entity |
| Predicate | chairmanIsUsually |
P18413
|
FINISHED |
| Object | High Court judge |
—
|
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: High Court judge | Statement: [Law Commission, chairmanIsUsually, High Court judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chairmanIsUsually Context triple: [Law Commission, chairmanIsUsually, High Court judge]
-
A.
hasChairmanTitle
Indicates that an entity holds the position or official title of chairman in relation to another entity or organization.
-
B.
chairperson
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
C.
chairmanshipRotates
Indicates that the role of chairperson is periodically transferred from one individual or entity to another according to a set rotation.
-
D.
coChairpersonOf
Indicates that a person serves jointly with one or more others as the chairperson of a group, organization, or committee.
-
E.
leaderIsUsually
chosen
Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5ca94c8190aa3771925913defc |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.