Triple
T1148976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Antonio de Padua |
E23630
|
entity |
| Predicate | underwentSecularization |
P26074
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mission San Antonio de Padua, underwentSecularization, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentSecularization Context triple: [Mission San Antonio de Padua, underwentSecularization, yes]
-
A.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
B.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
C.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
D.
disestablishmentEvent
Indicates the event or process by which an organization, institution, or system is formally dissolved, abolished, or stripped of its official status.
-
E.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:44 p.m.