Triple
T2001518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community of Christ |
E43480
|
entity |
| Predicate | hasTemplePurpose |
P35039
|
FINISHED |
| Object | worship |
—
|
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: worship | Statement: [Community of Christ, hasTemplePurpose, worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTemplePurpose Context triple: [Community of Christ, hasTemplePurpose, worship]
-
A.
templeType
Indicates the specific category or classification of a temple in terms of its form, function, or religious/architectural style.
-
B.
hadTempleDedicatedTo
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb880c710819098fb877052ce56dc |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:37 p.m.