Triple
T27459715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond |
E692697
|
entity |
| Predicate | hasReligiousInstitutionPresence |
P45908
|
FINISHED |
| Object | LDS meetinghouses |
—
|
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: LDS meetinghouses | Statement: [Raymond, hasReligiousInstitutionPresence, LDS meetinghouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligiousInstitutionPresence Context triple: [Raymond, hasReligiousInstitutionPresence, LDS meetinghouses]
-
A.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
hasDenominationalPresence
chosen
Indicates that a particular religious denomination is present or represented within a given location, organization, or context.
-
D.
hasReligiousBuildingAlong
Indicates that a religious building is located along the course, path, or extent of the referenced entity.
-
E.
hasPlaceOfWorship
Indicates that an entity possesses, contains, or is associated with a designated location used for religious or spiritual worship.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: April 27, 2026, 12:49 p.m.