Triple
T1071948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Carlos Borromeo de Carmelo |
E23348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Spanish mission |
C3699
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Spanish mission Context triple: [Mission San Carlos Borromeo de Carmelo, instanceOf, Spanish mission]
-
A.
Spanish colonial settlement
chosen
A Spanish colonial settlement is a community established by Spain in its overseas territories, typically organized around a central plaza with religious, administrative, and economic institutions to control, convert, and manage local populations and resources.
-
B.
Spanish colonial institution
A Spanish colonial institution is an organization or system established by the Spanish Empire to administer, control, and exploit its overseas territories through political, economic, religious, and social structures.
-
C.
Roman Catholic mission network
A Roman Catholic mission network is an organized system of churches, religious orders, and agencies that coordinate evangelization, pastoral care, education, and charitable works to spread and sustain the Catholic faith across different regions and cultures.
-
D.
former Spanish possession
A former Spanish possession is a territory or colony that was once under the sovereignty or administrative control of the Spanish Crown but is no longer governed by Spain.
-
E.
mission system
A mission system is a coordinated set of processes, tools, and resources designed to plan, execute, monitor, and evaluate the completion of specific operational or strategic objectives.
- F. None of above.
Provenance (1 batch)
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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.