Triple
T20845922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Appeal of Belize |
E513224
|
entity |
| Predicate | regionOfLaw |
P6190
|
FINISHED |
| Object | Belizean law |
—
|
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: Belizean law | Statement: [Court of Appeal of Belize, regionOfLaw, Belizean law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLaw Context triple: [Court of Appeal of Belize, regionOfLaw, Belizean law]
-
A.
legalSystemRegion
Indicates the geographic or jurisdictional region within which a particular legal system is applicable or in force.
-
B.
legalJurisdiction
chosen
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
C.
countryJurisdiction
Indicates that one country has legal authority, control, or governing power over a specified territory, entity, or matter.
-
D.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
-
E.
legalProtectionJurisdiction
Indicates the jurisdiction or legal authority under which an entity is granted legal protection.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34ec254819082610264c7af20c8 |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.