Triple
T10800156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | circuit court |
E254815
|
entity |
| Predicate | isPresidedOverBy |
P2725
|
FINISHED |
| Object | 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: judge | Statement: [circuit court, isPresidedOverBy, judge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPresidedOverBy Context triple: [circuit court, isPresidedOverBy, judge]
-
A.
alsoPresidedBy
Indicates that an event, organization, or proceeding is jointly overseen or led by an additional presiding entity alongside the primary one.
-
B.
presidedAt
Indicates that one entity held a position of authority or leadership over the proceedings or activities that took place at a specific event or location.
-
C.
councilPresidedOverBy
Indicates that a council or formal assembly is led, directed, or overseen by a particular person or authority.
-
D.
chamberPresidedOver
Indicates that one entity serves as the presiding authority or leader over the proceedings and activities of a specific chamber (such as a legislative or judicial body).
-
E.
hasPresidingOfficer
chosen
Indicates that one entity serves as the presiding officer (leader or chair) over another entity, such as an organization, meeting, or body.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733366c408190bfd3b57be5ef2440 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.