Triple
T1240424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Justice |
E26644
|
entity |
| Predicate | mayChair |
P377
|
FINISHED |
| Object | judicial council (in some jurisdictions) |
—
|
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: judicial council (in some jurisdictions) | Statement: [Chief Justice, mayChair, judicial council (in some jurisdictions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayChair Context triple: [Chief Justice, mayChair, judicial council (in some jurisdictions)]
-
A.
chairingSystem
Indicates that an entity is responsible for leading, overseeing, or presiding over a particular system or organized structure.
-
B.
maySitByRight
Indicates that an entity has the right or permission to sit next to another entity.
-
C.
chairperson
chosen
Indicates that one entity serves as the leader or head of a group, committee, or organization in relation to another entity.
-
D.
maySitEnBanc
Indicates that a judicial body has the authority or option to convene and hear a case with all (or a large majority of) its judges sitting together as a full court.
-
E.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf4343e48190a232abd8475880a0 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.