Triple
T32472202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Clerical Court |
E829876
|
entity |
| Predicate | appealAuthority |
P1031
|
FINISHED |
| Object | Supreme Leader or his delegate |
E21293
|
NE 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: Supreme Leader or his delegate | Statement: [Special Clerical Court, appealAuthority, Supreme Leader or his delegate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealAuthority Context triple: [Special Clerical Court, appealAuthority, Supreme Leader or his delegate]
-
A.
appealsFrom
chosen
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
B.
appealBasis
Indicates the grounds, reasons, or legal basis on which an appeal is made.
-
C.
appeal
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
- F. None of above.
Provenance (4 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a346699d02c8190ab26f2cd9fd9e5b5 |
completed | June 18, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 12:57 a.m.