Triple
T32472508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Courts of Iran |
E829883
|
entity |
| Predicate | appealsUltimatelyTo |
P35238
|
FINISHED |
| Object | Supreme Court of Iran |
—
|
NE NERFINISHED |
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 Court of Iran | Statement: [General Courts of Iran, appealsUltimatelyTo, Supreme Court of Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appealsUltimatelyTo Context triple: [General Courts of Iran, appealsUltimatelyTo, Supreme Court of Iran]
-
A.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
B.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
C.
appealsGoTo
Indicates that appeals arising from a decision or judgment are directed to and handled by a specified higher authority or court.
-
D.
ultimateAppealLiesTo
chosen
Indicates that the final level of appeal or review authority for a decision or case rests with a specified entity or body.
-
E.
alsoAppealsTo
Indicates that something attracts, interests, or is pleasing to an additional person, group, or audience beyond the primary one.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 12:57 a.m.