Triple
T23736440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi judiciary |
E586552
|
entity |
| Predicate | appliesBranchOfLaw |
P113669
|
FINISHED |
| Object | family law |
—
|
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: family law | Statement: [Saudi judiciary, appliesBranchOfLaw, family law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesBranchOfLaw Context triple: [Saudi judiciary, appliesBranchOfLaw, family law]
-
A.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
B.
appliesToFieldOfLaw
chosen
Indicates that something is relevant or applicable to a particular field or branch of law.
-
C.
appliedLawFrom
Indicates that a specific law or legal provision was applied or derived from a particular source, context, or jurisdiction in a legal decision or situation.
-
D.
appliesLawThrough
Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
-
E.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad28fa481909d7a6a6e98a7b0a5 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.