Triple
T34673307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debswana |
E890433
|
entity |
| Predicate | hasGovernmentPartner |
P87176
|
FINISHED |
| Object | Government of Botswana |
—
|
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: Government of Botswana | Statement: [Debswana, hasGovernmentPartner, Government of Botswana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentPartner Context triple: [Debswana, hasGovernmentPartner, Government of Botswana]
-
A.
partnerInGovernmentWith
Indicates that two entities share a formal partnership or coalition role within the same governmental structure or administration.
-
B.
governmentPartner
chosen
Indicates that one entity collaborates with or is formally partnered with a government or governmental body in some capacity.
-
C.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
D.
hasPartnerOrganization
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
-
E.
hasGlobalPartner
Indicates that an entity maintains a formal partnership or collaborative relationship with another entity at an international or worldwide level.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:05 a.m.