Triple
T9220894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الركن الأسود |
E221355
|
entity |
| Predicate | hasLegalRuling |
P2931
|
FINISHED |
| Object | استلامه وتقبيله سنة مؤكدة عند القدرة |
—
|
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: استلامه وتقبيله سنة مؤكدة عند القدرة | Statement: [الركن الأسود, hasLegalRuling, استلامه وتقبيله سنة مؤكدة عند القدرة]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalRuling Context triple: [الركن الأسود, hasLegalRuling, استلامه وتقبيله سنة مؤكدة عند القدرة]
-
A.
legalRulingNature
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
B.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
C.
hasLowerCourtDecision
Indicates that a higher court case is associated with, or results from, a specific decision made by a lower court.
-
D.
hasJustice
Indicates that an entity possesses, upholds, or embodies justice in its actions, qualities, or governing principles.
-
E.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda75b6888190814cfb890e763b8f |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.