Triple
T29483009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Courts of Sudan |
E747841
|
entity |
| Predicate | typeOfLitigant |
P26870
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [Public Courts of Sudan, typeOfLitigant, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLitigant Context triple: [Public Courts of Sudan, typeOfLitigant, individuals]
-
A.
litigantStatus
Indicates the legal role or standing a party holds in a lawsuit or legal proceeding (e.g., plaintiff, defendant, appellant).
-
B.
partyTypePlaintiffs
chosen
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
D.
legalCaseRole
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
E.
partyTypeOfRespondent
Indicates the specific legal or procedural role that the respondent plays as a party in a case or proceeding.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: April 28, 2026, 4:05 p.m.