Triple
T1071972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Carlos Borromeo de Carmelo |
E23348
|
entity |
| Predicate | missionChainOrder |
P23951
|
FINISHED |
| Object | second of the 21 California missions |
—
|
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: second of the 21 California missions | Statement: [Mission San Carlos Borromeo de Carmelo, missionChainOrder, second of the 21 California missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionChainOrder Context triple: [Mission San Carlos Borromeo de Carmelo, missionChainOrder, second of the 21 California missions]
-
A.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
-
B.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
-
C.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
D.
missionExtension
Indicates that an existing mission is being prolonged beyond its originally planned duration or scope.
-
E.
ordination
Indicates the formal conferral of religious authority or office upon a person within a religious tradition.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9296c5c8190a3060fbfdf24f029 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8d5076481908640a0d873efdf14 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.