Triple
T6517429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cow |
E148299
|
entity |
| Predicate | containsLegalRulingsOn |
P28367
|
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: [The Cow, containsLegalRulingsOn, prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLegalRulingsOn Context triple: [The Cow, containsLegalRulingsOn, prayer]
-
A.
legalRulingNature
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
B.
hasLegalRelevanceIn
Indicates that something is legally significant, applicable, or has consequences within a specified legal context, case, or jurisdiction.
-
C.
hasRulingInFiqh
Indicates that a subject has an associated legal ruling or judgment within the framework of Islamic jurisprudence (fiqh).
-
D.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
E.
jurisprudenceDiscussedIn
chosen
Indicates that a topic, issue, or principle of jurisprudence is examined, analyzed, or debated within a particular document, discussion, or source.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0ece2081909c14accef90efd7c |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.