Triple
T21180803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Province of San Francisco |
E521944
|
entity |
| Predicate | regionWithinUSCCB |
P143188
|
FINISHED |
| Object | Region XI |
—
|
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: Region XI | Statement: [Province of San Francisco, regionWithinUSCCB, Region XI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionWithinUSCCB Context triple: [Province of San Francisco, regionWithinUSCCB, Region XI]
-
A.
isRegionalJurisdictionOf
Indicates that one entity functions as the governing or administrative authority over a specific geographic region or area.
-
B.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
C.
isCentralJurisdictionOf
Indicates that a jurisdiction serves as the primary or main governing authority for a specified area, system, or set of entities.
-
D.
isInUSState
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
E.
regionalLocationWithinState
Indicates that one region is geographically located within the boundaries of a specific state.
- F. None of above. chosen
Provenance (4 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301da0ac8190a965fee7b6d845e7 |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:01 p.m.