Triple
T25335005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Demerara-Berbice |
E635251
|
entity |
| Predicate | partOfRegionSystem |
P38421
|
FINISHED |
| Object | Regions of Guyana |
—
|
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: Regions of Guyana | Statement: [Upper Demerara-Berbice, partOfRegionSystem, Regions of Guyana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRegionSystem Context triple: [Upper Demerara-Berbice, partOfRegionSystem, Regions of Guyana]
-
A.
regionalSystem
Indicates that something functions as or belongs to a system organized at a regional (sub-national or multi-local) level.
-
B.
partOfResourceRegion
Indicates that one resource is contained within, or forms a component of, a larger resource-defined region.
-
C.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
D.
isRegionOf
chosen
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
E.
partOfElectoralRegionSystem
Indicates that an electoral region belongs to, or is included within, a specific overarching electoral region system or framework.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 21, 2026, 1:32 p.m.