Triple
T165136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Third District Court of Appeal |
E2997
|
entity |
| Predicate | hears |
P5630
|
FINISHED |
| Object | civil 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: civil appeals | Statement: [California Third District Court of Appeal, hears, civil appeals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hears Context triple: [California Third District Court of Appeal, hears, civil appeals]
-
A.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
B.
heads
Indicates that one entity leads, directs, or is in charge of another entity, such as an organization, group, or initiative.
-
C.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
D.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a256eb46ec81909c730000e5041d0d |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.