Triple
T27209142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manaoag Church |
E683951
|
entity |
| Predicate | pastoralCareBy |
P18415
|
FINISHED |
| Object | Dominican Order |
—
|
NE NERFINISHED |
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: Dominican Order | Statement: [Manaoag Church, pastoralCareBy, Dominican Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastoralCareBy Context triple: [Manaoag Church, pastoralCareBy, Dominican Order]
-
A.
hasPastoralCareSystem
Indicates that an entity has an organized system or framework in place to provide pastoral or personal care and support to individuals.
-
B.
pastoralGoal
Indicates that an entity has a religious or spiritual care objective directed toward another entity or group.
-
C.
pastoralPurpose
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
-
D.
hasPastoralMission
chosen
Indicates that an entity is responsible for providing spiritual care, guidance, or religious leadership to a community or group.
-
E.
usesPastoralSetting
Indicates that the action or work is set in an idealized rural or countryside environment characteristic of pastoral themes.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f625e6cd708190aea9dc220df25717 |
completed | May 2, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:39 a.m.