Triple
T28831999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of the Holy Cross on Aghtamar |
E728073
|
entity |
| Predicate | occasionallyUsedForReligiousServices |
P86920
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cathedral of the Holy Cross on Aghtamar, occasionallyUsedForReligiousServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occasionallyUsedForReligiousServices Context triple: [Cathedral of the Holy Cross on Aghtamar, occasionallyUsedForReligiousServices, yes]
-
A.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
B.
churchUsedAs
chosen
Indicates that a church building is being utilized or repurposed for a particular function, activity, or role.
-
C.
usedAsChurchUntil
Indicates that something served the function or role of a church up to a specified point in time.
-
D.
hasDenominationalUse
Indicates that something is used or applied within the context of a particular religious denomination or sect.
-
E.
usedAsChurchFrom
Indicates that something functioned or was utilized as a church starting from a specified point in time.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593d67d48190af4c50e85c604a37 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:38 a.m.