Triple
T37102719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contra Costa County and Solano County |
E918747
|
entity |
| Predicate | shareRegionName |
P117178
|
FINISHED |
| Object | North Bay–East Bay interface |
—
|
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: North Bay–East Bay interface | Statement: [Contra Costa County and Solano County, shareRegionName, North Bay–East Bay interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareRegionName Context triple: [Contra Costa County and Solano County, shareRegionName, North Bay–East Bay interface]
-
A.
shareRegionalIdentityWith
chosen
Indicates that two entities are perceived to belong to or identify with the same geographic, cultural, or regional community.
-
B.
provinceSharesNameWith
Indicates that two provinces have exactly the same name, even if they are distinct administrative entities.
-
C.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
D.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
-
E.
sharesNameRootWith
Indicates that two entities have names derived from the same linguistic root or base form.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: May 3, 2026, 4:14 p.m.