Triple
T1240401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Justice |
E26644
|
entity |
| Predicate | typicallyPresidesOver |
P2725
|
FINISHED |
| Object | full court sittings |
—
|
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: full court sittings | Statement: [Chief Justice, typicallyPresidesOver, full court sittings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyPresidesOver Context triple: [Chief Justice, typicallyPresidesOver, full court sittings]
-
A.
alsoPresidedBy
Indicates that an event, organization, or proceeding is jointly overseen or led by an additional presiding entity alongside the primary one.
-
B.
presidingBody
Indicates the organization or authority that officially oversees, directs, or governs a given event, process, or body.
-
C.
hasPresidingOfficer
chosen
Indicates that one entity serves as the presiding officer (leader or chair) over another entity, such as an organization, meeting, or body.
-
D.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
-
E.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
- 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.