Triple
T4713543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Orthodox Memorial Park |
E104574
|
entity |
| Predicate | observesRite |
P28133
|
FINISHED |
| Object | Orthodox Trisagion service |
—
|
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: Orthodox Trisagion service | Statement: [Greek Orthodox Memorial Park, observesRite, Orthodox Trisagion service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesRite Context triple: [Greek Orthodox Memorial Park, observesRite, Orthodox Trisagion service]
-
A.
observedInRite
Indicates that an entity participates in or is witnessed as part of a specific ritual or ceremonial practice.
-
B.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
-
C.
containsRite
chosen
Indicates that one entity includes or incorporates a specific rite as part of its structure, content, or practice.
-
D.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
E.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.