Triple
T2091657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judicial Branch of California |
E32683
|
entity |
| Predicate | numberOfCourtsOfAppealDistricts |
P4502
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Judicial Branch of California, numberOfCourtsOfAppealDistricts, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCourtsOfAppealDistricts Context triple: [Judicial Branch of California, numberOfCourtsOfAppealDistricts, 6]
-
A.
numberOfCourts
chosen
Indicates the quantity of courts associated with or present at a given entity or location.
-
B.
judicialCircuit
Indicates the judicial circuit within which a legal entity, case, or jurisdiction is organized or falls under authority.
-
C.
numberOfDistricts
Indicates the total count of districts associated with a given entity or area.
-
D.
hasAppellateJurisdictionIn
Indicates that one legal authority has the power to review and decide appeals arising from cases within a specified court, region, or jurisdiction.
-
E.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba7626d081908c9c0f18942e128d |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.