Triple
T30537964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socal |
E777199
|
entity |
| Predicate | regionNameContains |
P67829
|
FINISHED |
| Object | 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: California | Statement: [Socal, regionNameContains, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionNameContains Context triple: [Socal, regionNameContains, California]
-
A.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
B.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
C.
toponymContains
chosen
Indicates that one geographic place name spatially includes or encompasses another place name within its boundaries.
-
D.
regionNameUsedFor
Indicates that a particular region name is used to refer to or designate a specific region or area.
-
E.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 29, 2026, 8:19 p.m.