Triple
T8433891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapel of Unity |
E199178
|
entity |
| Predicate | denominationalCharacter |
P83342
|
FINISHED |
| Object | ecumenical |
—
|
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: ecumenical | Statement: [Chapel of Unity, denominationalCharacter, ecumenical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationalCharacter Context triple: [Chapel of Unity, denominationalCharacter, ecumenical]
-
A.
denominationalOrientation
Indicates the specific religious denomination or sect with which an entity is formally affiliated or aligned.
-
B.
denominations
Indicates the specific units or categories into which something (often money, values, or items) is divided or classified.
-
C.
denominationalStatus
Indicates the religious denomination or sect to which an entity is formally affiliated or classified.
-
D.
denominationalControl
Indicates that an organization, institution, or entity is governed, overseen, or significantly influenced by a specific religious denomination.
-
E.
hasDenominationalUse
Indicates that something is used or applied within the context of a particular religious denomination or sect.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:07 p.m.