Triple
T34673390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTC Botswana |
E890435
|
entity |
| Predicate | handlesResource |
P28567
|
FINISHED |
| Object | diamonds from Botswana mines |
—
|
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: diamonds from Botswana mines | Statement: [DTC Botswana, handlesResource, diamonds from Botswana mines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesResource Context triple: [DTC Botswana, handlesResource, diamonds from Botswana mines]
-
A.
handlesMaterial
chosen
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
-
B.
handlesAgent
Indicates that one entity is responsible for managing, dealing with, or taking care of another entity (the agent).
-
C.
handlesFrom
Indicates that one entity is responsible for managing, processing, or dealing with something originating from another entity.
-
D.
handlesInterface
Indicates that one entity is responsible for managing, implementing, or interacting with a specified interface.
-
E.
handledWith
Indicates that an entity is managed, processed, or dealt with using a particular method, tool, or means.
- 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_69f7232166488190939c02bdaeacb490 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.