Triple
T5582037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Virginia |
E146661
|
entity |
| Predicate | hasDiscretionaryReview |
P8869
|
FINISHED |
| Object | most appeals |
—
|
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: most appeals | Statement: [Supreme Court of Virginia, hasDiscretionaryReview, most appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscretionaryReview Context triple: [Supreme Court of Virginia, hasDiscretionaryReview, most appeals]
-
A.
isDiscretionary
Indicates that the action or decision is optional and left to personal or organizational judgment rather than being mandatory or automatic.
-
B.
canReview
chosen
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
C.
hasReviewPeriod
Indicates that an entity is associated with a specific time span during which it is subject to review or evaluation.
-
D.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
E.
areReviewedEvery
Indicates that one entity conducts reviews of another entity at every specified time interval or on every relevant occasion.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208333f08190bf0049b6bdd280f5 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.