Triple
T7704290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unitarian Universalism |
E174573
|
entity |
| Predicate | worshipOftenHeldIn |
P71341
|
FINISHED |
| Object | meeting house |
—
|
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: meeting house | Statement: [Unitarian Universalism, worshipOftenHeldIn, meeting house]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worshipOftenHeldIn Context triple: [Unitarian Universalism, worshipOftenHeldIn, meeting house]
-
A.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
-
B.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
C.
worshipArea
chosen
Indicates a spatial or locational relationship where an area is designated or used for worship or religious practices.
-
D.
worshipPeriod
Indicates the time span or specific period during which an act of worship or religious devotion takes place.
-
E.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.