Triple
T24085874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cederberg Mountains |
E596640
|
entity |
| Predicate | hasEconomicActivityNearby |
P71206
|
FINISHED |
| Object | rooibos cultivation |
—
|
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: rooibos cultivation | Statement: [Cederberg Mountains, hasEconomicActivityNearby, rooibos cultivation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEconomicActivityNearby Context triple: [Cederberg Mountains, hasEconomicActivityNearby, rooibos cultivation]
-
A.
nearbyEconomicActivity
chosen
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
-
B.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
C.
hasMajorCompanyNearby
Indicates that a location or entity is situated close to at least one large or significant company.
-
D.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
E.
hasNearbyEconomicRegion
Indicates that one economic region is geographically close to or adjacent to another economic region.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc2a76c881908ee6e599dc6d155e |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:44 p.m.