Triple
T37145840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mai-Mai Kata Katanga |
E920236
|
entity |
| Predicate | regionIs |
P202077
|
FINISHED |
| Object | mineral-rich Katanga |
—
|
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: mineral-rich Katanga | Statement: [Mai-Mai Kata Katanga, regionIs, mineral-rich Katanga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionIs Context triple: [Mai-Mai Kata Katanga, regionIs, mineral-rich Katanga]
-
A.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
B.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
E.
regionID
Indicates that an entity is associated with, located in, or belongs to a specific geographic or administrative region identified by this ID.
- F. None of above. chosen
Provenance (4 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
| PDg | Predicate description generation | batch_6a004c41009c8190b18e41acf1fd7372 |
completed | May 10, 2026, 9:13 a.m. |
Created at: May 3, 2026, 4:15 p.m.