Triple
T165139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Third District Court of Appeal |
E2997
|
entity |
| Predicate | reviewsFor |
P1394
|
FINISHED |
| Object | errors of law |
—
|
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: errors of law | Statement: [California Third District Court of Appeal, reviewsFor, errors of law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reviewsFor Context triple: [California Third District Court of Appeal, reviewsFor, errors of law]
-
A.
reviewedBy
chosen
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
B.
peerReview
Indicates that one entity evaluates, critiques, or validates the work or performance of another entity, typically as an equal in expertise or status.
-
C.
implementsRecommendationOf
Indicates that one entity carries out or puts into practice a recommendation that was proposed or issued by another entity.
-
D.
canRecommend
Indicates that one entity is able or authorized to suggest or endorse another entity as suitable or preferable.
-
E.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a258827da481909b20ea5e9d21676f |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.