Triple
T35129786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rule 45 – Appeal by Certiorari to the Supreme Court |
E1014405
|
entity |
| Predicate | modeOfReview |
P67205
|
FINISHED |
| Object | petition for review on certiorari |
—
|
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: petition for review on certiorari | Statement: [Rule 45 – Appeal by Certiorari to the Supreme Court, modeOfReview, petition for review on certiorari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfReview Context triple: [Rule 45 – Appeal by Certiorari to the Supreme Court, modeOfReview, petition for review on certiorari]
-
A.
reviewType
chosen
Indicates the specific category or kind of review associated with an item, action, or relationship.
-
B.
reviewMethod
Indicates the method or process by which something is examined, evaluated, or reviewed.
-
C.
reviewModel
Indicates that an entity evaluates, critiques, or assesses another entity according to a particular standard or criteria.
-
D.
reviewOutcome
Indicates the result or conclusion reached after evaluating or reviewing something.
-
E.
reviewOf
Indicates that one entity is a critical or evaluative assessment that is about or directed toward 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c66345081909bed56b0b3686432 |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.