Triple
T34541285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Delta State |
E886812
|
entity |
| Predicate | hasMultipleJudicialDivisions |
P6714
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [High Court of Delta State, hasMultipleJudicialDivisions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleJudicialDivisions Context triple: [High Court of Delta State, hasMultipleJudicialDivisions, true]
-
A.
hasCourtDivision
Indicates that a court is organized into, or belongs to, a specific internal division or section within the judicial system.
-
B.
hasJudicialDistrict
Indicates that an entity falls within or is associated with a specific judicial district for legal or court-related purposes.
-
C.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
D.
hasBranchCourts
chosen
Indicates that an institution or main court maintains one or more subordinate or satellite courts under its jurisdiction.
-
E.
separatesJurisdiction
Indicates that one entity establishes a boundary or distinction that divides the legal authority or governance area of another entity.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 1, 2026, 2:02 a.m.