Triple
T13982756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grace |
E336354
|
entity |
| Predicate | hasLiveWorshipAtmosphere |
P112038
|
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: [Grace, hasLiveWorshipAtmosphere, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveWorshipAtmosphere Context triple: [Grace, hasLiveWorshipAtmosphere, true]
-
A.
hasWorshipServices
Indicates that an entity conducts or provides organized religious worship services.
-
B.
worshipArea
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
-
C.
hasWorshipSpaceFeature
Indicates that a worship space possesses or includes a particular feature, characteristic, or facility.
-
D.
hasLiturgicalSpace
Indicates that one entity provides or contains a designated space used for liturgical or religious worship activities in relation to another entity.
-
E.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea2e8808190a1203a6386224bd8 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:18 p.m.