Triple
T37524912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circuit Courts of Ghana |
E932882
|
entity |
| Predicate | evidenceLaw |
P16442
|
FINISHED |
| Object | Evidence Act of Ghana |
—
|
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: Evidence Act of Ghana | Statement: [Circuit Courts of Ghana, evidenceLaw, Evidence Act of Ghana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceLaw Context triple: [Circuit Courts of Ghana, evidenceLaw, Evidence Act of Ghana]
-
A.
evidenceAtIssue
Indicates that a particular piece of evidence is directly contested, disputed, or central to the disagreement or decision in a case or situation.
-
B.
evidenceHandling
Indicates how evidence is collected, processed, stored, and transferred within an investigation or legal context.
-
C.
lawJournal
Indicates a relationship where a work is published in, associated with, or appears within a specific law journal.
-
D.
appliesRulesOfEvidence
Indicates that one party enforces or follows established rules of evidence in relation to another party or proceeding.
-
E.
law
chosen
Indicates that one entity establishes, embodies, or enforces a rule or system of rules governing the behavior or relations 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.