Triple
T212852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharia |
E4754
|
entity |
| Predicate | includesObligation |
P6254
|
FINISHED |
| Object | prayer |
—
|
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: prayer | Statement: [Sharia, includesObligation, prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesObligation Context triple: [Sharia, includesObligation, prayer]
-
A.
obligation
chosen
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
-
B.
obligationType
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
C.
isSubjectTo
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
D.
obligorText
Indicates that one entity is described as the party bearing the obligation or debt toward another entity, typically in a contractual or financial context.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c313d108190a65d3e939f961bef |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.