Triple
T12784343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabot |
E305584
|
entity |
| Predicate | ifAbsent |
P30856
|
FINISHED |
| Object | Divine Liturgy may not be celebrated in that church |
—
|
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: Divine Liturgy may not be celebrated in that church | Statement: [Tabot, ifAbsent, Divine Liturgy may not be celebrated in that church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ifAbsent Context triple: [Tabot, ifAbsent, Divine Liturgy may not be celebrated in that church]
-
A.
succeedsInAbsenceOf
chosen
Indicates that one entity successfully achieves or maintains something only when another specified entity or condition is not present.
-
B.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
existsIf
Indicates that the existence or validity of one entity or condition depends on the presence or truth of another specified condition.
-
D.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
E.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
- 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e5cb3c08190b8e1e22de8b96e17 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:29 p.m.