Triple
T34055818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pastoral Ministries |
E873351
|
entity |
| Predicate | locationInstitution |
P205295
|
FINISHED |
| Object | Sun Valley, California |
E205675
|
NE 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: Sun Valley, California | Statement: [Pastoral Ministries, locationInstitution, Sun Valley, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInstitution Context triple: [Pastoral Ministries, locationInstitution, Sun Valley, California]
-
A.
locatedAtInstitution
Indicates that an entity is situated at, based in, or physically present within a particular institution.
-
B.
homeInstitutionLocation
Indicates the geographic place where an entity’s primary or home institution is located.
-
C.
memberInstitutionLocation
Indicates that a member institution is located in, or associated with, a specific geographic place or address.
-
D.
inInstitution
Indicates that an entity is located within, belongs to, or is formally associated with a particular institution.
-
E.
cityOfInstitution
Indicates the city in which an institution is located or based.
- F. None of above. chosen
Provenance (5 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36ae476a588190944b05a7ff913e52 |
completed | June 20, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:52 a.m.