Triple
T22015003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Soledad |
E543685
|
entity |
| Predicate | foundedInChain |
P70349
|
FINISHED |
| Object | California mission chain |
—
|
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: California mission chain | Statement: [Mission Soledad, foundedInChain, California mission chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedInChain Context triple: [Mission Soledad, foundedInChain, California mission chain]
-
A.
foundedAsNumberInChain
chosen
Indicates that an entity was established as the N-th member or location in a sequential chain (e.g., the 3rd branch or franchise).
-
B.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
C.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
D.
foundedWith
Indicates that an entity was established or created together with another entity, typically as co-founders or jointly initiated partners.
-
E.
foundationFoundedIn
Indicates that a foundation was established or came into existence in a specific year or time period.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a774548190bcd98dc28f2d2c5f |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:22 p.m.