Triple
T25898807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulwich Prep London |
E652544
|
entity |
| Predicate | hasPastoralCareFocus |
P172089
|
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: [Dulwich Prep London, hasPastoralCareFocus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastoralCareFocus Context triple: [Dulwich Prep London, hasPastoralCareFocus, yes]
-
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.
hasPastoralMission
Indicates that an entity is responsible for providing spiritual care, guidance, or religious leadership to a community or group.
-
C.
hasPastoralCenter
Indicates that an entity possesses or is associated with a pastoral center as one of its facilities or organizational components.
-
D.
hasPastoralStructure
Indicates that an entity possesses or is organized according to a pastoral (shepherding or ministerial) governance or structural arrangement.
-
E.
hasPastoralArea
Indicates that one entity is assigned to, responsible for, or associated with a specific pastoral area or pastoral care region of another 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_69e7ab3c6cc081908de59bfcc28ec19d |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 22, 2026, 8:23 a.m.