Triple
T6392628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Buenaventura |
E143864
|
entity |
| Predicate | returnedToChurch |
P70350
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Mission San Buenaventura, returnedToChurch, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToChurch Context triple: [Mission San Buenaventura, returnedToChurch, late 19th century]
-
A.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
hasParentChurch
Indicates that a church or religious organization is institutionally subordinate to or derived from another church, which serves as its parent or overseeing body.
-
D.
associatedWithChurch
Indicates a relationship in which an entity has a connection, involvement, or affiliation with a church.
-
E.
returnedToFamilyHomeBy
Indicates that an entity has been brought or taken back to their family home by another specified entity.
- 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_69c008db906c819096f3597d55d95432 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0687f5c6c81909c835329c996b311 |
completed | March 22, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69c060f25c088190b433f78553ff1d84 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.