Triple
T34513012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marist College Ashgrove |
E886073
|
entity |
| Predicate | hasPastoralCareProgram |
P195352
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Marist College Ashgrove, hasPastoralCareProgram, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastoralCareProgram Context triple: [Marist College Ashgrove, hasPastoralCareProgram, true]
-
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.
hasPastoralCareFocus
Indicates that the subject is oriented toward providing spiritual, emotional, or pastoral support and guidance to others.
-
C.
hasPastoralPrograms
chosen
Indicates that an entity offers or conducts pastoral care or ministry programs.
-
D.
hasPastoralMission
Indicates that an entity is responsible for providing spiritual care, guidance, or religious leadership to a community or group.
-
E.
hasPastoralCenter
Indicates that an entity possesses or is associated with a pastoral center as one of its facilities or organizational components.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 1, 2026, 2:01 a.m.