Triple
T29197899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite Divine Liturgy |
E740179
|
entity |
| Predicate | commonAnaphora |
P192291
|
FINISHED |
| Object | Anaphora of Sharar |
—
|
NE NERFINISHED |
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: Anaphora of Sharar | Statement: [Maronite Divine Liturgy, commonAnaphora, Anaphora of Sharar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonAnaphora Context triple: [Maronite Divine Liturgy, commonAnaphora, Anaphora of Sharar]
-
A.
usesAnaphora
Indicates that one entity refers back to another previously mentioned entity using anaphoric expression (e.g., pronouns or repeated phrases).
-
B.
hasAnaphora
Indicates that one expression in a text refers back to another earlier expression for its interpretation.
-
C.
hasPrincipalAnaphora
Indicates that one element serves as the primary anaphoric reference (main referring expression) for another element within a discourse or text.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity or context.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 28, 2026, 12:05 p.m.