Triple
T165160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Third District Court of Appeal |
E2997
|
entity |
| Predicate | cannotConduct |
P3971
|
FINISHED |
| Object | jury trials |
—
|
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: jury trials | Statement: [California Third District Court of Appeal, cannotConduct, jury trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotConduct Context triple: [California Third District Court of Appeal, cannotConduct, jury trials]
-
A.
doesNotParticipateIn
chosen
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
-
B.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
cannotHearCasesFrom
Indicates that one entity lacks the authority or ability to hear, consider, or adjudicate cases originating from another entity.
-
E.
canEnforce
Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon 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_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.