Triple
T31529432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohairic region |
E804436
|
entity |
| Predicate | hasEcclesiasticalUse |
P25209
|
FINISHED |
| Object | Bohairic liturgical texts |
—
|
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: Bohairic liturgical texts | Statement: [Bohairic region, hasEcclesiasticalUse, Bohairic liturgical texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEcclesiasticalUse Context triple: [Bohairic region, hasEcclesiasticalUse, Bohairic liturgical texts]
-
A.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
B.
churchUsedAs
Indicates that a church building is being utilized or repurposed for a particular function, activity, or role.
-
C.
hasEcclesiasticalImportance
Indicates that something holds significant religious or church-related authority, influence, or relevance within an ecclesiastical context.
-
D.
hasDenominationalUse
chosen
Indicates that something is used or applied within the context of a particular religious denomination or sect.
-
E.
usedAsChurchUntil
Indicates that something served the function or role of a church up to 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10 p.m.