Triple
T25335010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Demerara-Berbice |
E635251
|
entity |
| Predicate | containsMiningCommunity |
P42429
|
FINISHED |
| Object | Ituni |
—
|
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: Ituni | Statement: [Upper Demerara-Berbice, containsMiningCommunity, Ituni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMiningCommunity Context triple: [Upper Demerara-Berbice, containsMiningCommunity, Ituni]
-
A.
hasMiningCommunities
chosen
Indicates that one entity possesses, contains, or is associated with communities whose primary activity is mining.
-
B.
isFormerMiningCommunity
Indicates that a place was historically a mining community but no longer functions primarily as one.
-
C.
hasNearbyFormerMiningCommunity
Indicates that an entity is located close to a community that previously hosted mining activities but is no longer an active mining site.
-
D.
containsMiningTown
Indicates that a location or area includes within its boundaries a town whose primary activity or identity is based on mining.
-
E.
isMiningTown
Indicates that a location is a town whose primary historical or economic basis is mining activities.
- 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.