Triple
T5663775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine liturgical calendar |
E124805
|
entity |
| Predicate | structures |
P4621
|
FINISHED |
| Object | worship life |
—
|
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: worship life | Statement: [Byzantine liturgical calendar, structures, worship life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structures Context triple: [Byzantine liturgical calendar, structures, worship life]
-
A.
constructs
Indicates that an agent builds, creates, or assembles something, typically resulting in a new or more complex entity or structure.
-
B.
buildingStructure
Indicates that one entity is a structural component or physical part that forms, supports, or constitutes the construction of another entity.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
massiveStructure
Indicates that an entity is a very large or imposing physical structure in terms of size, scale, or mass.
-
E.
architecture
chosen
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
- 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.