Triple
T23736453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudi judiciary |
E586552
|
entity |
| Predicate | allowsAppealsTo |
P17875
|
FINISHED |
| Object | courts of appeal |
—
|
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: courts of appeal | Statement: [Saudi judiciary, allowsAppealsTo, courts of appeal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsAppealsTo Context triple: [Saudi judiciary, allowsAppealsTo, courts of appeal]
-
A.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
B.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
C.
canBeAppealedTo
chosen
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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.