Triple
T30006737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rancho San Leandro |
E762342
|
entity |
| Predicate | subsequentJurisdiction |
P18056
|
FINISHED |
| Object | U.S. state of California |
—
|
NE NERFINISHED |
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: U.S. state of California | Statement: [Rancho San Leandro, subsequentJurisdiction, U.S. state of California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentJurisdiction Context triple: [Rancho San Leandro, subsequentJurisdiction, U.S. state of California]
-
A.
laterLegalJurisdiction
chosen
Indicates that one legal jurisdiction succeeds or replaces another jurisdiction at a later point in time.
-
B.
subsequentCase
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
-
C.
successorJurisdictionFunction
Indicates that one jurisdictional authority or function has been succeeded or taken over by another, establishing a continuity of jurisdictional responsibility.
-
D.
subsequentCounty
Indicates that one county follows another in a defined sequence, such as chronological order of creation or administrative succession.
-
E.
jurisdictionTransferred
Indicates that legal authority or control over a matter, case, or entity has been moved from one jurisdiction to another.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6795282648190a8351e4cbace98d3 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:43 p.m.