Triple

T25814967
Position Surface form Disambiguated ID Type / Status
Subject administrative courts of Egypt E650222 entity
Predicate hearCasesAgainst P18526 FINISHED
Object ministries 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: ministries | Statement: [administrative courts of Egypt, hearCasesAgainst, ministries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hearCasesAgainst
Context triple: [administrative courts of Egypt, hearCasesAgainst, ministries]
  • A. hearsCasesAgainst chosen
    Indicates that one party (typically a judicial body or official) formally listens to and considers legal cases brought against another party.
  • B. hearCasesBroughtBy
    Indicates that a judicial body or authority formally considers and adjudicates legal cases initiated by a particular party or group.
  • C. hearsCasesAs
    Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
  • D. hearsAppealsAgainst
    Indicates that one entity formally reviews and considers appeals challenging the decisions or actions of another entity.
  • E. hearsCasesWith
    Indicates that one judicial body or judge conducts proceedings together with another judicial body or judge in hearing the same cases.
  • 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_69e7ab367fcc8190a5ff1e7f3da046a4 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f600c84ac4819091492e52a5a8b873 completed May 2, 2026, 1:48 p.m.
PD Predicate disambiguation batch_69f5afec3e94819080d9ba86cf8c866e completed May 2, 2026, 8:03 a.m.
Created at: April 22, 2026, 7:25 a.m.