Triple
T29448755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Californias (historical) |
E746922
|
entity |
| Predicate | formerSubregion |
P30672
|
FINISHED |
| Object | Alta 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: Alta California | Statement: [The Californias (historical), formerSubregion, Alta California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerSubregion Context triple: [The Californias (historical), formerSubregion, Alta California]
-
A.
formerSubdivisionOf
chosen
Indicates that an entity once functioned as an administrative or territorial part of another entity but no longer holds that status.
-
B.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
-
C.
subregionOf
Indicates that one region is geographically or administratively contained within, and is a part of, another larger region.
-
D.
subnationalRegion
Indicates that one region is a subdivision or administrative part of a larger nation or country.
-
E.
subregionName
Indicates that one region is identified by a specific name used for a smaller or subordinate geographic or administrative area within a larger region.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: April 28, 2026, 3:30 p.m.