Triple
T34446029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mvelaphanda Group |
E884228
|
entity |
| Predicate | hasPrimaryOperationsIn |
P156737
|
FINISHED |
| Object | South Africa |
E3669
|
NE 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: South Africa | Statement: [Mvelaphanda Group, hasPrimaryOperationsIn, South Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryOperationsIn Context triple: [Mvelaphanda Group, hasPrimaryOperationsIn, South Africa]
-
A.
hasMainOperations
Indicates that an entity is associated with its primary or core operations, activities, or functions.
-
B.
hasOperationsIn
Indicates that an entity conducts business activities or maintains operational presence within a specified location or region.
-
C.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
D.
hasBasedOperations
chosen
Indicates that one entity conducts or maintains its primary operations or activities at the location or facility represented by another entity.
-
E.
hasGlobalOperationsIn
Indicates that an entity conducts business or operational activities across multiple countries within the specified region or location.
- F. None of above.
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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0309a4e4d481908a6070b40d507aae |
completed | May 12, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3729cf58b88190b6d7f92e590f5d51 |
completed | June 21, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_6a03091ac1008190bf50357364d4e9e4 |
completed | May 12, 2026, 11:03 a.m. |
Created at: May 1, 2026, 2 a.m.