Triple
T32768716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Collegium for Civil Cases |
E837974
|
entity |
| Predicate | reviewForm |
P67205
|
FINISHED |
| Object | collegial consideration of cases by a panel of judges |
—
|
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: collegial consideration of cases by a panel of judges | Statement: [Judicial Collegium for Civil Cases, reviewForm, collegial consideration of cases by a panel of judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewForm Context triple: [Judicial Collegium for Civil Cases, reviewForm, collegial consideration of cases by a panel of judges]
-
A.
reviewFormat
Indicates the specific structure, style, or medium in which a review is presented or delivered.
-
B.
reviewType
chosen
Indicates the specific category or kind of review associated with an item, action, or relationship.
-
C.
reviewModel
Indicates that an entity evaluates, critiques, or assesses another entity according to a particular standard or criteria.
-
D.
reviewFrom
Indicates that a review is authored or provided by a particular source or entity.
-
E.
reviewFunction
Indicates that one entity serves the role or function of reviewing, evaluating, or assessing 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.